Hide Forgot
This is following a discussion on fedora-devel. See http://lists.fedoraproject.org/pipermail/devel/2011-November/160025.html We're using dracut net bootings to mount systems with iscsi root disks. The dhcp root-path option is being used to specify the root iscsi device. We're using the old network system rather than networkmanager. The root disk is marked with the _netdev option in /etc/fstab. On shutdown/reboot, the network is shutdown before the system reboots. Bill Nottingham provided a patch: http://lists.fedoraproject.org/pipermail/devel/2011-November/160095.html This didn't work because a) The exit statement in the read loop only exits the read loop! b) "findmnt -m -n -o fstype,options /" doesn't show the _netdev option even though fstab has it (presumably because dracut mounted it?) This patch works http://lists.fedoraproject.org/pipermail/devel/2011-November/160108.html Because 1) I added an extra exit statement to break if the loop breaked 2) I told findmnt to look in fstab (-s) Note that the iscsid startup script also has an incorrect check to see whether the root is on a _netdev device.
Karel - you had mentioned that '-m' looks at /run/mount/utab. However, I'm not seeing that ever get populated in testing here. Under what cases will it?
(In reply to comment #1) > Karel - you had mentioned that '-m' looks at /run/mount/utab. However, I'm not > seeing that ever get populated in testing here. Under what cases will it? You have to mount with userspace specific mount option (e.g. _netdev, user=, ...). The filesystem has to be mounted by mount(8) or /sbin/mount.nfs. The another utils or mount helpers are not linked with libmount (yet). Do you really have the latest F16 util-linux (mount and switch_root) in dracut? Is there /run when you call the mount? I have never tested this functionality for root device :-) Note that switch_root(8) from util-linux < 2.20.1 does not move /run from initrd to the real root device. Anyway, _netdev works for me for regular devices: # rpm -qf /bin/mount util-linux-2.20.1-2.1.fc16.x86_64 # echo "/dev/sdb1 /mnt ext3 defaults,_netdev" >> /etc/fstab # mount /mnt # findmnt --noheadings --mtab /mnt -o OPTIONS rw,relatime,errors=continue,barrier=0,data=ordered,_netdev # cat /run/mount/utab SRC=/dev/sdb1 TARGET=/mnt ROOT=/ OPTS=_netdev
OK, so we can either: a) rely on fstab, for now, and not catch things that have been randomly mounted with _netdev b) rely on mtab/utab, but only catch mounted-in-booted-system things until we do some dracut, etc. fixes Hm, maybe try both and use all the results in the meantime?
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.