[Bug 878473] New: After installation is system not able to mount non-root lvm volumes
https://bugzilla.novell.com/show_bug.cgi?id=878473 https://bugzilla.novell.com/show_bug.cgi?id=878473#c0 Summary: After installation is system not able to mount non-root lvm volumes Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: werner@suse.com ReportedBy: tcech@suse.com QAContact: jsrain@suse.com CC: fcrozat@suse.com Found By: L3 Blocker: --- 1] This doesn't look like installation issue, but more like dracut/systemd/lvm2 problem. Change component if you want. 2] I'm not using any snapshot, but network yast installation of factory repository System reach emergency mode - the state requesting entering root password (or pressing Ctrl-D). Checking `journalctl -xb' tells me, that: Job dev-venom-gentoo.device/start timed out. gentoo.mount has failed local-fs.target has failed systemd-fsck@dev-venom-gentoo.service has failed This also repeats for devel, home, data (this one is luks) LVM modules. ls /dev/venom # venom is the name of volume group opensuse That is LVM volume with root filesystem and is the only one which is mounted. Running vgchange -a y venom makes them all available. I'm also not prompted for password for encrypted volume. After calling systemd-tty-ask-password-agent Also data volume is correctly mounted. I'll try to attach output of `journalctl -xb' soon. Bug reported from tablet. -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c1
--- Comment #1 from Tomas Cech
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c2
Tomas Cech
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c3
--- Comment #3 from Tomas Cech
Checking `journalctl -xb' tells me, that: Job dev-venom-gentoo.device/start timed out. gentoo.mount has failed local-fs.target has failed systemd-fsck@dev-venom-gentoo.service has failed
This also repeats for devel, home, data (this one is luks) LVM modules.
LVM _volumes_, sorry... -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c4
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c5
Thomas Blume
May 17 08:48:22 linux-ys02 LVM: Logical Volume autoactivation enabled.
I'm heavily suspecting an issue with lvmetad. Can you please set: use_lvmetad = 0 in /etc/lvm/lvm.conf and check wheter this solves the issue? -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c6
Tomas Cech
The log shows:
May 17 08:48:22 linux-ys02 LVM: Logical Volume autoactivation enabled.
I'm heavily suspecting an issue with lvmetad. Can you please set:
use_lvmetad = 0
in /etc/lvm/lvm.conf and check wheter this solves the issue?
Yes, it does! -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c7
Thomas Blume
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c9
Tomas Cech
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c10
Thomas Blume
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c11
--- Comment #11 from Tomas Cech
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c12
--- Comment #12 from dong mao zhang
Both are disabled. Dong, this seems to be a regression of bug #862076. lvm2-lvmetad.socket should be always active. Can you please check? Yes, you are right. we should set lvm2 socket avaliable. I have already add '%service_add_post lvm2-lvmetad.socket' in the %POST section in spec.
But It seems the macro %service_add_post does not support the socket files. Can you bring the maintainer of this macro into this bug? -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c13
--- Comment #13 from Frederic Crozat
(In reply to comment #10)
Both are disabled. Dong, this seems to be a regression of bug #862076. lvm2-lvmetad.socket should be always active. Can you please check? Yes, you are right. we should set lvm2 socket avaliable. I have already add '%service_add_post lvm2-lvmetad.socket' in the %POST section in spec.
But It seems the macro %service_add_post does not support the socket files.
It does. Of course, if you expect the socket and the service to be enabled by default with this macro, they should be part of the preset package (cf http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines ) -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c14
--- Comment #14 from dong mao zhang
(In reply to comment #12)
(In reply to comment #10)
Both are disabled. Dong, this seems to be a regression of bug #862076. lvm2-lvmetad.socket should be always active. Can you please check? Yes, you are right. we should set lvm2 socket avaliable. I have already add '%service_add_post lvm2-lvmetad.socket' in the %POST section in spec.
But It seems the macro %service_add_post does not support the socket files.
It does.
Of course, if you expect the socket and the service to be enabled by default with this macro, they should be part of the preset package (cf http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines )
OK, I will send a patch to preset the lvmetad.socket enabled as default. -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c15
--- Comment #15 from dong mao zhang
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c16
--- Comment #16 from Frederic Crozat
Could systemd-presets-branding support this socket file as well? I want the lvmetad.socket enabled, lvmetad.service disable as default.
Both need to be enabled, but the service won't be started until it is asked by the socket. -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c17
--- Comment #17 from dong mao zhang
(In reply to comment #15)
Could systemd-presets-branding support this socket file as well? I want the lvmetad.socket enabled, lvmetad.service disable as default.
Both need to be enabled, but the service won't be started until it is asked by the socket.
My solution to this is below: 1. set lvmetad.socket and lvmetad.service enabled in systemd-presets-branding. 2. call "systemctl enable lvmetad.socket" in %POST section 3. call 'systemctl start lvmetad.socket' in %POST section Normally, we do not want lvmetad started until asked. But I do not understand why we need to set lvmetad.service enabled in systemd-preset. From my perspective, only enabling lvmetad.socket is good enough. -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c18
--- Comment #18 from Frederic Crozat
(In reply to comment #16)
(In reply to comment #15)
Could systemd-presets-branding support this socket file as well? I want the lvmetad.socket enabled, lvmetad.service disable as default.
Both need to be enabled, but the service won't be started until it is asked by the socket.
My solution to this is below: 1. set lvmetad.socket and lvmetad.service enabled in systemd-presets-branding. 2. call "systemctl enable lvmetad.socket" in %POST section
2 is not needed if you rely on the presets branding package (otherwise you are hardcoding a policy in a package).
3. call 'systemctl start lvmetad.socket' in %POST section
Normally, we do not want lvmetad started until asked.
-- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c19
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c20
--- Comment #20 from Thomas Blume
https://bugzilla.novell.com/show_bug.cgi?id=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c21
Liuhua Wang
(In reply to comment #15)
Could systemd-presets-branding support this socket file as well? I want the lvmetad.socket enabled, lvmetad.service disable as default.
Both need to be enabled, but the service won't be started until it is asked by the socket.
If lvm2-lvmetad.service is enabled in systemd-presets-branding, when machine reboots, lvm2-lvmetad.service will be running, which is not what we wanted, so I don't think we need to add "enable lvm2-lvemetad.service" in systemd-presets-branding, am I right? -- 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=878473
https://bugzilla.novell.com/show_bug.cgi?id=878473#c22
Neil Rickert
participants (1)
-
bugzilla_noreply＠novell.com