FS#32680 - [mkinitcpio] disable lvmetad to suppress warning

Attached to Project: Arch Linux
Opened by Christian Hesse (eworm) - Thursday, 15 November 2012, 11:08 GMT
Last edited by Dave Reisner (falconindy) - Monday, 10 December 2012, 15:45 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Eric Belanger (Snowman)
Thomas Bächler (brain0)
Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Shutting down a system with LVM results in this warning:

WARNING: Failed to connect to lvmetad: Connection refused. Falling back to internal scanning.

This patch alters lvm.conf to disable lvmetad in shutdown hook.

Additional info:
mkinitcpio 0.11.0-1
   mkinitcpio_lvm.patch (0.4 KiB)
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 10 December 2012, 15:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  mkinitcpio 0.12.0
Comment by Thomas Bächler (brain0) - Thursday, 15 November 2012, 12:27 GMT
I think Dave had another solution for this already.
Comment by Dave Reisner (falconindy) - Thursday, 15 November 2012, 12:29 GMT
I thought I did, but I can't recall what I had in mind. Anyways, there's no chance of this patch being applied.
Comment by Thomas Bächler (brain0) - Thursday, 15 November 2012, 12:39 GMT
You used the environment to override the path to the LVM config files in /run/initramfs/shutdown.

My idea would be to simply delete lvm.conf in cleanup.
Comment by Dave Reisner (falconindy) - Thursday, 15 November 2012, 13:24 GMT
I guess whether we point at /dev/null or delete the config is irrelephant as it's the same effect. The question is whether or not this causes problems for someone who needs some config bits from the file (I can't see why this would be, but I don't claim to know LVM). I quickly perused the code and didn't see any way to disable only this.
Comment by Thomas Bächler (brain0) - Thursday, 15 November 2012, 15:11 GMT
Basically, the configuration is only relevant for activating, creating, destroying and scanning for volumes or volume groups. Once active, all knowledge about them should be configured in the kernel's dm tables. I think you could even use 'dmsetup remove' to disable the volumes without any ill-effects.
Comment by Dave Reisner (falconindy) - Thursday, 15 November 2012, 15:29 GMT
oooh, didn't realize that was a possibility, but it makes perfect sense. Bonus -- the patch ends up being about removing code, rather than adding it.
Comment by Dave Reisner (falconindy) - Sunday, 02 December 2012, 15:28 GMT
If you're using testing, this was implemented in 0.12.0.

Loading...