[Bug 1230010] New: /.snapshots not mountable during boot
https://bugzilla.suse.com/show_bug.cgi?id=1230010 Bug ID: 1230010 Summary: /.snapshots not mountable during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc@user.net Reporter: kukuk@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877086 --> https://bugzilla.suse.com/attachment.cgi?id=877086&action=edit journalctl -b output I had this now the second time in a few days, every time a different MicroOS machine: after reboot machine is stuck in sulogin, because /.snapshots could not be mounted. Reading the logs I noticed that wtmpdb got again started before dbus-broker, but I don't know if the wrong ordering is a followup error or the root cause (see bsc#1229813). This machine is using systemd-boot with FDE+TPM. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c1 --- Comment #1 from Thorsten Kukuk <kukuk@suse.com> --- Created attachment 877087 --> https://bugzilla.suse.com/attachment.cgi?id=877087&action=edit systemctl status for /.snapshots -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c2 --- Comment #2 from Thorsten Kukuk <kukuk@suse.com> --- Created attachment 877088 --> https://bugzilla.suse.com/attachment.cgi?id=877088&action=edit dmesg output -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com, | |simonf.lees@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 Alberto Planas Dominguez <aplanas@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aplanas@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c3 --- Comment #3 from Thorsten Kukuk <kukuk@suse.com> --- I have to correct: this machine is using standard grub2 and no FDE... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c4 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk@suse.com Flags| |needinfo?(kukuk@suse.com) --- Comment #4 from Fabian Vogt <fvogt@suse.com> --- The error message can be misleading: libmount shows the first mount of the source device if the mount syscall returns -EBUSY for whatever reason. In this case the most likely reason for that is that /.snapshots is already mounted. Is this reproducible? When the error happens, is /.snapshots already mounted? If not, what happens on systemctl start /.snapshots? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c5 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kukuk@suse.com) | --- Comment #5 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to Fabian Vogt from comment #4)
The error message can be misleading: libmount shows the first mount of the source device if the mount syscall returns -EBUSY for whatever reason. In this case the most likely reason for that is that /.snapshots is already mounted.
Is this reproducible?
No, it's not. I saw this now during 3 days on two machines, all the other machines and this ones rebooted without problems the other times.
When the error happens, is /.snapshots already mounted? If not, what happens on systemctl start /.snapshots?
Forgot to check that. At least /.snapshots was mounted after I pressed Ctrl-D and could login. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c6 --- Comment #6 from Fabian Vogt <fvogt@suse.com> --- (In reply to Thorsten Kukuk from comment #5)
(In reply to Fabian Vogt from comment #4)
The error message can be misleading: libmount shows the first mount of the source device if the mount syscall returns -EBUSY for whatever reason. In this case the most likely reason for that is that /.snapshots is already mounted.
Is this reproducible?
No, it's not. I saw this now during 3 days on two machines, all the other machines and this ones rebooted without problems the other times.
When the error happens, is /.snapshots already mounted? If not, what happens on systemctl start /.snapshots?
Forgot to check that. At least /.snapshots was mounted after I pressed Ctrl-D and could login.
Ok, so the question is what mounts /.snapshots and why systemd didn't realize that before it attempted to start /.snapshots itself. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c7 --- Comment #7 from Fabian Vogt <fvogt@suse.com> --- (In reply to Fabian Vogt from comment #6)
(In reply to Thorsten Kukuk from comment #5)
(In reply to Fabian Vogt from comment #4)
The error message can be misleading: libmount shows the first mount of the source device if the mount syscall returns -EBUSY for whatever reason. In this case the most likely reason for that is that /.snapshots is already mounted.
Is this reproducible?
No, it's not. I saw this now during 3 days on two machines, all the other machines and this ones rebooted without problems the other times.
When the error happens, is /.snapshots already mounted? If not, what happens on systemctl start /.snapshots?
Forgot to check that. At least /.snapshots was mounted after I pressed Ctrl-D and could login.
Ok, so the question is what mounts /.snapshots and why systemd didn't realize that before it attempted to start /.snapshots itself.
To find out what else mounts /.snapshots, I commented out the entry in /etc/fstab and rebooted. The system booted successfully and /.snapshot was not mounted, so I failed to reproduce the issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230010 https://bugzilla.suse.com/show_bug.cgi?id=1230010#c13 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #13 from Fabian Vogt <fvogt@suse.com> --- Meanwhile the bug was investigated and fixed in bug 1231836, let's close this as duplicate. *** This bug has been marked as a duplicate of bug 1231836 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com