[Bug 1157147] New: loop devices missing after upgrade to TW 20191116
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 Bug ID: 1157147 Summary: loop devices missing after upgrade to TW 20191116 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: tjyrinki@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- /dev/loop* (including loop-control) are missing after upgrading to 20191116 and rebooting. Not sure what should be creating them and why would they be missing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c1 --- Comment #1 from Timo Jyrinki <tjyrinki@suse.com> --- Manually doing: mknod /dev/loop-control c 10 237 Fixes the problem at least temporarily. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c2 --- Comment #2 from Timo Jyrinki <tjyrinki@suse.com> --- I've tried on another laptop I have and it did not break with the upgrade, so it does not happen everywhere. On this problematic system the kernel module 'loop' is not loaded automatically for some reason. Another temporary workaround would be "modprobe loop", and a more permanent workaround adding a file /etc/modules-load.d/loop.conf with content "loop" in it. Getting further in understanding this problem would be to know in which way(s) the loop module should be automatically loaded and why it's not happening in this case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c5 Timo Jyrinki <tjyrinki@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tjyrinki@suse.com | |) | --- Comment #5 from Timo Jyrinki <tjyrinki@suse.com> --- No change when switching to 5.3.9-1, still needs the workaround. I can't currently pinpoint anything. The only facts I know that before Tuesday when I started my work week I didn't notice anything broken (it's quite visible since I use snap apps in dash-to-dock favorites so a big icon immediately vanishes if loop devices do not work), and I started my work week by shutting down and trying the new GNOME option that said something like "Install updates before shutting down". After booting back up, I noticed an icon missing and started debugging. There are uncertainties related to how long uptime it was before the updates / reboot, but I'm relatively certain I had rebooted after TW 20191112 update already because I've had some Thunderbolt USB device disappears that vanish with a reboot. So far it seems it's just me, and even though I'd like to understand the root problem very much, I'm ok also if this bug is closed without finding it and I can stick to my workaround. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- OK, then another question is whether loop kernel module gets loaded as default. Usually when the module is loaded, /dev/loop* devices are created automatically. It's possible that some of your machines have loop module loaded by some reason, while another not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c7 --- Comment #7 from Timo Jyrinki <tjyrinki@suse.com> --- Yes, this is what I described in comment #2, the loop module isn't automatically loaded, and I'm trying to find a root cause in case it would be something that could affect others besides me. Loading the loop module creates the device nodes, so the original bug description which I cannot change and comment #1 are irrelevant at this point. The workaround is forcing its load via /etc/modules-load.d. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c8 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Assignee|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- Well, then the problem is not about the kernel itself. The loop module has been always independent and optional. So if anything happened, it must be outside the kernel packaging. Reassigned the component. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |jslaby@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c14 Timo Jyrinki <tjyrinki@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(tjyrinki@suse.com | |) | --- Comment #14 from Timo Jyrinki <tjyrinki@suse.com> --- I removed the workaround /etc/modules.load.d/loop.conf I had added, and now that I'm at Tumbleweed 20191124 I can't reproduce the problem anymore after rebooting :( I tried booting back to previous kernel 5.3.11-1 but that does not bring the problem back, so it wasn't a kernel change. After the last reboot test without workaround on Thursday I did not do anything other as root than upgrading packages. Maybe it was system configuration related problem that got properly fixed by a suitable upgrade, for example regenerated initrd, but it's really hard to say. With no way to reproduce this for others or myself, I'm setting this as resolved/worksforme. Thank you everyone, I hope it breaks again some day so that I could at least get a hang of what is happening. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c1 --- Comment #1 from Timo Jyrinki <tjyrinki@suse.com> --- Manually doing: mknod /dev/loop-control c 10 237 Fixes the problem at least temporarily. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c2 --- Comment #2 from Timo Jyrinki <tjyrinki@suse.com> --- I've tried on another laptop I have and it did not break with the upgrade, so it does not happen everywhere. On this problematic system the kernel module 'loop' is not loaded automatically for some reason. Another temporary workaround would be "modprobe loop", and a more permanent workaround adding a file /etc/modules-load.d/loop.conf with content "loop" in it. Getting further in understanding this problem would be to know in which way(s) the loop module should be automatically loaded and why it's not happening in this case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c5 Timo Jyrinki <tjyrinki@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tjyrinki@suse.com | |) | --- Comment #5 from Timo Jyrinki <tjyrinki@suse.com> --- No change when switching to 5.3.9-1, still needs the workaround. I can't currently pinpoint anything. The only facts I know that before Tuesday when I started my work week I didn't notice anything broken (it's quite visible since I use snap apps in dash-to-dock favorites so a big icon immediately vanishes if loop devices do not work), and I started my work week by shutting down and trying the new GNOME option that said something like "Install updates before shutting down". After booting back up, I noticed an icon missing and started debugging. There are uncertainties related to how long uptime it was before the updates / reboot, but I'm relatively certain I had rebooted after TW 20191112 update already because I've had some Thunderbolt USB device disappears that vanish with a reboot. So far it seems it's just me, and even though I'd like to understand the root problem very much, I'm ok also if this bug is closed without finding it and I can stick to my workaround. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- OK, then another question is whether loop kernel module gets loaded as default. Usually when the module is loaded, /dev/loop* devices are created automatically. It's possible that some of your machines have loop module loaded by some reason, while another not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c7 --- Comment #7 from Timo Jyrinki <tjyrinki@suse.com> --- Yes, this is what I described in comment #2, the loop module isn't automatically loaded, and I'm trying to find a root cause in case it would be something that could affect others besides me. Loading the loop module creates the device nodes, so the original bug description which I cannot change and comment #1 are irrelevant at this point. The workaround is forcing its load via /etc/modules-load.d. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1157147 http://bugzilla.opensuse.org/show_bug.cgi?id=1157147#c8 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Assignee|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- Well, then the problem is not about the kernel itself. The loop module has been always independent and optional. So if anything happened, it must be outside the kernel packaging. Reassigned the component. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com