- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- umount nfs cdrom
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-27-2002 12:49 PM
тАО12-27-2002 12:49 PM
umount nfs cdrom
According to the man page, can't manually edit this file. any suggestion on delete this line?
problem : nfs server still not responding...
in /etc/fstab, there are no present of nfs mount
already stop all of the nfs daemon (server, client and core) in addition, also edit the rc.config.d nfsconf file...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-27-2002 08:59 PM
тАО12-27-2002 08:59 PM
Re: umount nfs cdrom
If you get that message then it is better to reboot the server and see that the nfs is prperly umounted . An improer umount results in such errors . This will also result in an incomplter list os bdf etc bcoz it check for the mounted partions . You canoot edit mnntab , all you can do it rename it and then do a mount -a which will recreate the mnntab , but this will not help nfs server not responding message . yopu will have to reboot the server .
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2002 02:35 AM
тАО12-28-2002 02:35 AM
Re: umount nfs cdrom
mv /etc/mnttab /etc/mnttab.old
mount -a
lsof "mount point of cdrom"
note down the processes accessing that file
do a ps -ef |grep for those process ids & terminate them....
do
/sbin/init.d/nfs.client stop # I assume there are no nfs mounted directories if there umount them for a while....
/sbin/init.d/nfs.client start
Cheers,
kaps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2002 08:33 AM
тАО12-30-2002 08:33 AM
Re: umount nfs cdrom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2002 10:14 AM
тАО12-30-2002 10:14 AM
Re: umount nfs cdrom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2002 10:20 AM
тАО12-30-2002 10:20 AM
Re: umount nfs cdrom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2002 10:57 AM
тАО12-30-2002 10:57 AM
Re: umount nfs cdrom
"man mount_nfs". Has a section concerning hard vs. soft It seem to confuse more than clarify:
Hard vs. Soft
File systems that are mounted read-write or that contain executable files should always be mounted with the hard option. Applications using soft mounted file systems may incur unexpected I/O errors.
To improve NFS read performance, files and file attributes are cached. File modification times get updated whenever a write occurs. However, file access times may be temporarily out-of- date until the cache gets refreshed. The attribute cache retains file attributes on the client. Attributes for a file are assigned a time to be flushed. If the file is modified before the flush time, then the flush time is extended by the time since
the last modification (under the assumption that files that
changed recently are likely to change soon). There is a minimum and maximum flush time extension for regular files and for directories. Setting actimeo=n sets flush time to n seconds for both regular files and directories.
My experience is that you get I/O errors via NFS when the remote system becomes unavailble (crash), Or the network goes down. How you use the NFS filesystem might determine how you mount it. The reason why I have been using (for years) the soft mount option is to avoid problems like you are experiencing. We have yet to receive catastrophic I/O errors via NFS. However most of my remote mounts are used for "READS" a few have low write activity.
Ror