[Bug 699458] New: local fs mount times out for loop-mounted filesystem
https://bugzilla.novell.com/show_bug.cgi?id=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c0 Summary: local fs mount times out for loop-mounted filesystem Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: volker3204@paradise.net.nz QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.6; Linux) KHTML/4.6.0 (like Gecko) SUSE The boot process gets stuck for 30 (40?) seconds trying to mount a local file-system, increasing boot time by that much. System configuration: /dev/md0 / reiserfs ... /dev/md1 /home reiserfs ... /dev/sda6 /local/data reiserfs ... /local/data/backup.ext2 /local/lastbackup auto loop,defaults,ro,auto Booting is stuck on mounting backup.ext2 until timeout occurs. At a guess, boot.localfs fails to notice that the backup.ext2 file is located on a filesystem that is not yet mounted, hence attempting to mount it can not succeed. Used to work fine on oS 11.1. A similar problem for shutdown also prevents clean shutdown (although this is not the only problem preventing clean shutdowns). Neither /dev/sda6 nor /dev/md0 are unmounted during shutdown. /dev/md0 can't be unmounted because it has the mount point for a file from /dv/sda6, /dev/sda6 can't be un-mounted because one of its files remains in use. Reproducible: Always Steps to Reproduce: 1. Create system file-system config as detailed. 2. Reboot. 3. Watch boot screen. Expected Results: Mount file-systems in correct order at boot time. Un-mount file-systems in correct order during shutdown. -- 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=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c1 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volker3204@paradise.net.nz --- Comment #1 from Volker Kuhlmann <volker3204@paradise.net.nz> 2011-06-12 08:15:21 UTC --- The following two mounts /local/data/openSUSE-11.4-DVD-i586.iso /srv/ftp/suse11.4_32 iso9660 loop,ro,noauto 0 0 /local/data/openSUSE-11.4-DVD-x86_64.iso /srv/ftp/suse11.4_64 iso9660 loop,ro,noauto 0 0 when mounted before shutdown, prevent unmounting all filesystems on shutdown, although mounting read-only succeeds so clean shutdown is still theoretically possible. All loop-mounted file-systems should probably be unmounted before unmounting block-device-based file-systems. -- 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=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |ro@novell.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=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c2 Ruediger Oertel <ro@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com --- Comment #2 from Ruediger Oertel <ro@suse.com> 2012-03-19 13:18:07 UTC --- werner: I guess the sequencing code for mounting is not really ready for this, any idea ? -- 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=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|werner@suse.com | --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2012-03-19 13:28:18 UTC --- There was a change in aaa_base for loop devices, there I suggest to try the /etc/init.d/boot.localfs from 12.1 or factory. -- 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=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c4 Ruediger Oertel <ro@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |volker3204@paradise.net.nz --- Comment #4 from Ruediger Oertel <ro@suse.com> 2012-03-19 14:55:09 UTC --- hm, not just in aaa_base but also in util-linux for some cases, see https://bugzilla.novell.com/show_bug.cgi?id=666150 the change in aaa_base mainly boils down to: --- a/files/etc/init.d/boot.localfs +++ b/files/etc/init.d/boot.localfs @@ -87,9 +87,10 @@ list_missed () mount -afnv $mount_opts 2> /dev/null | while read line ; do dev="${line%% *}" case "$line" in + mount:\ *) continue ;; # messages from mount *mounted*) continue ;; - *) test -b $dev && continue + *) test -e $dev && continue echo "${dev}" ;; esac done does this help for your case already ? -- 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=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c5 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|volker3204@paradise.net.nz | --- Comment #5 from Volker Kuhlmann <volker3204@paradise.net.nz> 2012-03-23 00:25:08 NZDT --- I upgraded my last 11.4 to 12.1 2 weeks ago, so can no longer test for 11.4. Assume that it is not fixed. With 12.1 things only get worse. The loop mount during boot fails, the whole thing stops with fs mount error, wants root password. Nothing to do, exit shell. Seemingly after each single boot command the whole thing stops again, root password, ... This is useless. /etc/init.d/boot.localfs already contains the patch from comment #4. What is the recommended way to loop-mount iso (or other) images during boot? It used to just work. Well, without parallel booting anyway... -- 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=699458 https://bugzilla.novell.com/show_bug.cgi?id=699458#c6 Ruediger Oertel <ro@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #6 from Ruediger Oertel <ro@suse.com> 2013-11-11 16:42:48 UTC --- bug is probably obsolete with the switch to systemd, closing -- 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