[Bug 736826] New: boot hangs if comment=systemd.automount is used
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c0 Summary: boot hangs if comment=systemd.automount is used Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bartoschek@or.uni-bonn.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 Starting with 12.1 opensuse did not mount the nfs entries in the fstab on system boot. Some people on the opensuse mailinglist mentioned that one has to add comment=systemd.automount to the fstab entries to get them mounted. After adding the option however boot hangs. I've waited about 30 minutes before I removed the option in the single user mode. Here is the modified fstab: /dev/sda2 swap swap defaults 0 0 /dev/sda3 / ext4 acl,user_xattr 1 1 /dev/sda1 /boot ext2 acl,user_xattr 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 bate:/.../vlsi.uni-bonn.de/fs /dfs nfs rw,soft,intr,rsize=8192,wsize=8192,nfsvers=3,timeo=30,comment=systemd.automount 0 0 moebius.vlsi.uni-bonn.de:/usr/local /usr/local nfs ro,soft,intr,timeo=30,comment=systemd.automount 0 0 Besides the problem I expect that I do not have to add such a comment to the fstab to get this working. Reproducible: Always Steps to Reproduce: 1. Add comment=systemd.automount to an nfs mount 2. reboot 3. Actual Results: Boot hangs Expected Results: Boot works. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c1 Christoph Bartoschek <bartoschek@or.uni-bonn.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Critical --- Comment #1 from Christoph Bartoschek <bartoschek@or.uni-bonn.de> 2011-12-14 16:18:43 UTC --- The following is part of /var/log/messages around the hang. First the kernel loads till 14:49 then at 14:51 an timeout seems to be catched and networking appears to start. But then nothing happens till I rebooted the machine one hour later. Dec 14 14:49:52 conto kernel: [ 21.044641] Adding 35159036k swap on /dev/sda2. Priority:0 extents:1 across:35159036k Dec 14 14:49:52 conto kernel: [ 21.129520] e1000 0000:09:02.1: eth1: (PCI:66MHz:64-bit) 00:d0:68:08:39:23 Dec 14 14:49:52 conto kernel: [ 21.129526] e1000 0000:09:02.1: eth1: Intel(R) PRO/1000 Network Connection Dec 14 14:49:52 conto kernel: [ 21.129696] e1000 0000:08:02.0: PCI INT A -> GSI 54 (level, low) -> IRQ 54 Dec 14 14:49:52 conto kernel: [ 21.427121] e1000 0000:08:02.0: eth2: (PCI-X:100MHz:64-bit) 00:d0:68:08:39:20 Dec 14 14:49:52 conto kernel: [ 21.427133] e1000 0000:08:02.0: eth2: Intel(R) PRO/1000 Network Connection Dec 14 14:49:52 conto kernel: [ 21.427385] e1000 0000:08:02.1: PCI INT B -> GSI 55 (level, low) -> IRQ 55 Dec 14 14:49:52 conto kernel: [ 21.724510] e1000 0000:08:02.1: eth2: (PCI-X:100MHz:64-bit) 00:d0:68:08:39:21 Dec 14 14:49:52 conto kernel: [ 21.724513] e1000 0000:08:02.1: eth2: Intel(R) PRO/1000 Network Connection Dec 14 14:49:52 conto kernel: [ 22.179351] device-mapper: uevent: version 1.0.3 Dec 14 14:49:52 conto kernel: [ 22.179622] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: dm-devel@redhat.com Dec 14 14:49:52 conto haveged: haveged starting up Dec 14 14:49:52 conto haveged: arch: x86#012vendor: amd#012generic: 0#012i_cache: 64#012d_cache: 64#012loop_idx: 15#012loop_idxmax: 40#012loop_sz: 64806#012loop_szmax: 100861#012etime: 7959#012havege_ndpt 0 Dec 14 14:49:52 conto avahi-daemon[1104]: Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Dec 14 14:49:52 conto avahi-daemon[1104]: Successfully dropped root privileges. Dec 14 14:49:52 conto avahi-daemon[1104]: avahi-daemon 0.6.30 starting up. Dec 14 14:51:22 conto network[1056]: Failed to get D-Bus connection: Failed to authenticate in time. Dec 14 14:51:23 conto network[1056]: Hint: you may set mandatory devices in /etc/sysconfig/network/config Dec 14 14:51:23 conto network[1056]: Setting up network interfaces: Dec 14 14:51:23 conto network[1056]: lo Dec 14 14:51:23 conto ifup: lo Dec 14 14:51:23 conto ifup: lo Dec 14 14:51:23 conto ifup: IP address: 127.0.0.1/8 Dec 14 14:51:23 conto network[1056]: lo IP address: 127.0.0.1/8 Dec 14 14:51:23 conto ifup: Dec 14 14:51:23 conto network[1056]: ..done eth0 device: Intel Corporation 82557/8/9/0/1 Ethernet Pro Dec 14 14:51:23 conto ifup: eth0 device: Intel Corporation 82557/8/9/0/1 Ethernet Pro Dec 14 14:51:23 conto network[1056]: No configuration found for eth0 Dec 14 14:51:23 conto ifup: No configuration found for eth0 Dec 14 14:51:23 conto network[1056]: ..unused eth1 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:23 conto ifup: eth1 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:23 conto network[1056]: No configuration found for eth1 Dec 14 14:51:23 conto ifup: No configuration found for eth1 Dec 14 14:51:24 conto network[1056]: ..unused eth2 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:24 conto ifup: eth2 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:24 conto kernel: [ 114.740414] e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Dec 14 14:51:24 conto kernel: [ 114.744044] ADDRCONF(NETDEV_UP): eth2: link is not ready Dec 14 14:51:24 conto kernel: [ 114.748115] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Dec 14 14:51:24 conto ifup: eth2 Dec 14 14:51:24 conto ifup: IP address: 192.168.143.203/24 Dec 14 14:51:24 conto network[1056]: eth2 IP address: 192.168.143.203/24 Dec 14 14:51:24 conto ifup: Dec 14 14:51:24 conto network[1056]: ..done eth3 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:24 conto ifup: eth3 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:24 conto network[1056]: No configuration found for eth3 Dec 14 14:51:24 conto ifup: No configuration found for eth3 Dec 14 14:51:24 conto network[1056]: ..unused eth4 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:24 conto ifup: eth4 device: Intel Corporation 82546EB Gigabit Ethernet Co Dec 14 14:51:24 conto network[1056]: No configuration found for eth4 Dec 14 14:51:24 conto ifup: No configuration found for eth4 Dec 14 14:51:24 conto network[1056]: ..unusedSetting up service network . . . . . . . . ...done Dec 14 15:09:52 conto rsyslogd: -- MARK -- Dec 14 15:29:52 conto rsyslogd: -- MARK -- Dec 14 15:49:53 conto rsyslogd: -- MARK -- Dec 14 15:58:49 conto kernel: imklog 5.8.5, log source = /proc/kmsg started. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c Cristian Rodríguez <crrodriguez@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crrodriguez@opensuse.org AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c2 --- Comment #2 from Frederic Crozat <fcrozat@suse.com> 2011-12-16 09:39:12 UTC --- if you don't get nfs mountpoint working in "normal" conditions, adding comment=systemd.automount won't fix it. Do you have nfs mountpoint working when booting with sysvinit (press f5 at boot time and choose systemV) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c3 --- Comment #3 from Christoph Bartoschek <bartoschek@or.uni-bonn.de> 2011-12-16 09:57:34 UTC --- After enabling the nfs service it works when booting in sysvinit and in systemd. Without the nfs service it does not work with sysvinit. If you think that comment=systemd.automount is not supposed to work, you can close the issue. However there is one problem: The second mountpoint is mounted twice when I use the nfs service: conto:~ # rcnfs start redirecting to systemctl conto:~ # df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 206418360 8302512 187630040 5% / devtmpfs 33013952 52 33013900 1% /dev tmpfs 33054388 0 33054388 0% /dev/shm tmpfs 33054388 560 33053828 1% /run /dev/sda3 206418360 8302512 187630040 5% / tmpfs 33054388 0 33054388 0% /sys/fs/cgroup tmpfs 33054388 560 33053828 1% /var/lock tmpfs 33054388 560 33053828 1% /var/run tmpfs 33054388 0 33054388 0% /media /dev/sda1 232039 39978 180081 19% /boot moebius:/usr/local/ 48442368 18197504 27784192 40% /usr/local bate:/.../vlsi.uni-bonn.de/fs/ 9000000 0 9000000 0% /dfs moebius:/usr/local/ 48442368 18197504 27784192 40% /usr/local -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c4 --- Comment #4 from Frederic Crozat <fcrozat@suse.com> 2011-12-16 10:20:36 UTC --- it is mounted twice under systemd only ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c5 --- Comment #5 from Christoph Bartoschek <bartoschek@or.uni-bonn.de> 2011-12-16 10:21:53 UTC --- No. It does not depend on the init system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=736826 https://bugzilla.novell.com/show_bug.cgi?id=736826#c6 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #6 from Frederic Crozat <fcrozat@suse.com> 2011-12-16 10:33:18 UTC --- I suggest you open a new bug for this, then. closing this one as invalid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com