From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0
Description of problem:
'service netfs stop' does not unmount filesystems that have the _netdev option in /etc/fstab. Calling 'umount -a -O _netdev' (which is in netfs for _netdev devices) manually will unmount said filesystems. It appears that the problem is in how netfs detects which devices have the _netdev flag. It currently looks in /proc/mounts, but /proc/mounts does not list the _netdev flag. _netdev only shows up in /etc/mtab and the 'mount' command output.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a line to /etc/fstab for a filesystem, and add the _netdev option
/dev/sdd /mnt auto _netdev 0 0
2. mount the filesystem
# mount /mnt
3. run 'service netfs stop'
Actual Results: /dev/sdd is still mounted on /mnt
Expected Results: /dev/sdd should have been unmounted
_netdev is recommended by the iscsi-initiator-utils README as a method to mount and unmount iscsi devices. Currently when people use this method, their filesystems do not get unmounted, and the system crashes during the reboot process. (See bug #144781 for more information) Even without the crash, this could cause filesystem corruption since it is not cleanly unmounted before the network is shut off.
Created attachment 110890 [details]
Fix where netfs looks for _netdev info
Change netfs so it looks at /etc/mtab instead of /proc/mounts for the _netdev
This is creating serious heartburn for iSCSI users in RHEL 3. Will it be
possible to get the fix in U5? Thanks.
Fixed in 7.31.22.EL-1/7.93.13.EL-1.
*** Bug 148764 has been marked as a duplicate of this bug. ***
U1 fix confirmed in 7.93.13.EL-1, U5 fix confirmed in 7.31.22.EL-1. Moving to
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.