[Bug 661715] New: loop module not autoloaded on "mount -oloop"
https://bugzilla.novell.com/show_bug.cgi?id=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c0 Summary: loop module not autoloaded on "mount -oloop" Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: seife@novell.slipkontur.de QAContact: qa@suse.de Found By: Third Party Developer/Partner Blocker: --- susi:~ # mount /space/iso/SLES11/SLE-11-SP1-SDK-DVD-x86_64-GM-DVD1.iso /mnt/ -oloop,ro mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) susi:~ # modprobe loop susi:~ # mount /space/iso/SLES11/SLE-11-SP1-SDK-DVD-x86_64-GM-DVD1.iso /mnt/ -oloop,ro susi:~ # I faintly remember that I did not have to manually load the "loop" module before. I'm running FACTORY with systemd, just in case this makes a difference. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c wei wang <wewang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wewang@novell.com AssignedTo|bnc-team-screening@forge.pr |coolo@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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c1 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Stephan Kulow <coolo@novell.com> 2011-01-12 12:38:31 CET --- I'm running stock 11.3: mount: Konnte kein „loop“-Gerät finden. Vielleicht kennt dieser Kernel kein „loop“-Gerät? (Wenn dies der Fall ist, dann sollten Sie den Kernel neu kompilieren oder „modprobe loop“ ausführen.) -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c2 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-01-12 16:38:02 CET --- In stock 11.3, "modprobe loop" is called by boot.localfs, so I guess you must have changed something. Actually the same is true for factory, so systemd is probably not running boot.localfs and thus not loading the loop module. Maybe adding it as a default to "MODULES_LOADED_AT_BOOT" would be a good 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c3 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |kasievers@novell.com Resolution| |INVALID --- Comment #3 from Stephan Kulow <coolo@novell.com> 2011-01-13 10:44:21 CET --- your bug report was "loop module not autoloaded on mount" and I closed as INVALID because it doesn't do that 11.3 either. And I don't see any value in autoloading the loop module for the average user. So I disagree with your suggestion, even though I would add it myself. I'm not sure if we have a list of changes you inherit by switching to systemd, but it would be a good thing to collect. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c4 --- Comment #4 from Kay Sievers <kasievers@novell.com> 2011-01-13 10:08:17 UTC --- systemd has it's own config for force-loading modules: man modules-load.d which should be uses instead of anything in /etc/sysconfig/. The loopdev logic in the kernel is just utterly broken and needs to be fixed to have a control device (like /dev/mapper/control) for loop devices, instead of requiring an arbitrary number of pre-created loop devices, which might, or might be not be used, or might be too many or to few, later. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c5 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |lnussel@novell.com Resolution|INVALID | --- Comment #5 from Ludwig Nussel <lnussel@novell.com> 2011-01-21 13:23:59 CET --- I'm reopening this as boot.localfs does modprobe loop unconditionally. I only noticed because I accidentally broke it and it got restored. Autoloading the loop module on demand could be achieved by having a /dev/loop0 device node. So we could either patch an alias devname:loop0 into the loop module or package /lib/udev/devices/loop0. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c6 --- Comment #6 from Kay Sievers <kasievers@novell.com> 2011-01-21 16:27:06 UTC --- (In reply to comment #5)
patch an alias devname:loop0 into the loop module
This could not go upstream as is the wrong solution and papers over the real problem that loop in the kernel is just a broken concept regarding the device management. It would need a proper control device, like /dev/mapper/control is, or something similar.
or package /lib/udev/devices/loop0.
Enabling autoloading only loop0 access might work for the common case, but is still a hack. I guess loading loop.ko unconditionally from /etc/modules-load.d/ (and make sysv read that too) might be the best current option. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@novell.com |lnussel@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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c7 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #7 from Ludwig Nussel <lnussel@novell.com> 2011-01-25 10:55:11 CET --- I'd rather give the the /lib/udev/devices/ solution a try. Unconditionally loading the module is what we already have so it's hanging around even if not needed. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c8 Dirk Mueller <dmueller@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |dmueller@novell.com Resolution|FIXED | --- Comment #8 from Dirk Mueller <dmueller@novell.com> 2011-05-16 23:01:53 CEST --- which breaks LXC containers, as they disallow to create loop nodes: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /lib/udev/devices/loop0;4dd18fab: cpio: mknod failed - Operation not permitted -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c9 --- Comment #9 from Dirk Mueller <dmueller@novell.com> 2011-05-16 23:05:10 CEST --- the easiest solution is probably to not package the device node, but just generate it in %post - and silently ignore the failure if it doesn't work. but why was this ugly hack added to aaa_base in the first place and not udev? -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c10 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #10 from Ludwig Nussel <lnussel@novell.com> 2011-05-17 15:41:37 CEST --- done for Factory. Do we need an online update for 11.4? -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c11 --- Comment #11 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-05-17 16:00:16 CEST --- This is an autogenerated message for OBS integration: This bug (661715) was mentioned in https://build.opensuse.org/request/show/70460 Factory / aaa_base -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c12 --- Comment #12 from Marcus Meissner <meissner@novell.com> 2011-05-17 14:10:33 UTC --- lets do +1 -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c13 Christian Dengler <cdengler@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED CC| |cdengler@novell.com InfoProvider|maintenance@opensuse.org | --- Comment #13 from Christian Dengler <cdengler@novell.com> 2011-05-17 14:38:51 UTC --- okay, update started: SwampID 40961 -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c14 --- Comment #14 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-05-18 16:00:10 CEST --- This is an autogenerated message for OBS integration: This bug (661715) was mentioned in https://build.opensuse.org/request/show/70552 11.4 / aaa_base -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c15 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.4:41009 --- Comment #15 from Swamp Workflow Management <swamp@suse.com> 2011-05-31 13:39:07 UTC --- Update released for: aaa_base, aaa_base-debuginfo, aaa_base-debugsource, aaa_base-extras Products: openSUSE 11.4 (debug, i586, x86_64) -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c16 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #16 from Ludwig Nussel <lnussel@novell.com> 2011-06-01 16:07:29 CEST --- close as fixed again -- 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