Summary: | sys-fs/lvm2-2.02.109: lvmetad needs to create directory during boot | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | j.habenicht |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | rossi.f |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=521960 https://bugs.gentoo.org/show_bug.cgi?id=520738 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch to test for /run/lvm directory during boot |
Created attachment 387344 [details, diff]
patch to test for /run/lvm directory during boot
*** This bug has been marked as a duplicate of bug 521960 *** I'm experiencing the same problem on my system (i.e. lvmetad failure) but if fails for another reason different from the one pointed by #521960 In my case, during the boot runlevel, I get * Starting lvmetad ... * start-stop-daemon: fopen `/run/lvmetad.pid': No such file or directory * Detaching to start `/sbin/lvmetad' ... * start-stop-daemon: fopen `/run/lvmetad.pid': No such file or directory * start-stop-daemon: did not create a valid pid in `/run/lvmetad.pid' * Failed to start lvmetad [ !! ] * ERROR: cannot start lvm as lvmetad would not start while later in the default runlevel * Starting lvmetad ... * start-stop-daemon: fopen `/run/lvmetad.pid': No such file or directory * Detaching to start `/sbin/lvmetad' ... [ ok ] I have 'use_lvmetad = 0' in /etc/lvm/lvm.conf (so I don't understand why lvm is forced to depend unconditionally on lvmetad as suggested in #525614) and probably for this reason I don't see the error message regarding the /run/lvm/lvmetad.socket *** This bug has been marked as a duplicate of bug 521960 *** (In reply to Jeroen Roovers from comment #4) > > *** This bug has been marked as a duplicate of bug 521960 *** Jeroen, why is this bug duplicate of #521960? It seems that this one is related to the startup of lvmetad while the other reports a communication problem between lvmetad (so already started successfully) and lvm daemon. FYI I solved my problem with lvmetad as suggested in #1. I have 'use_lvmetad = 0' in /etc/lvm/lvm.conf so lvmetad is disabled |
Hello all, during the "boot" boot sequence lvmetad bailed out. It was restarted later during the "default" boot sequence. Reason is the directory /run/lvm is missing. A patch to the init script helped: 10a11,15 > start_pre() > { > checkpath --directory /var/run/lvm || return 1 > } > Reproducible: Always Steps to Reproduce: 1. install sys-fs/lvm2-2.02.109 2. boot in step mode ("I" keypress) 3. if lvmetad fails check for /run/lvm presence in shell ("4" keypress)