Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 526756 - sys-fs/lvm2-2.02.109: lvmetad needs to create directory during boot
Summary: sys-fs/lvm2-2.02.109: lvmetad needs to create directory during boot
Status: RESOLVED DUPLICATE of bug 521960
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-25 15:24 UTC by j.habenicht
Modified: 2014-11-12 22:24 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
patch to test for /run/lvm directory during boot (lvmetad.patch,85 bytes, patch)
2014-10-25 15:26 UTC, j.habenicht
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description j.habenicht 2014-10-25 15:24:55 UTC
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)
Comment 1 j.habenicht 2014-10-25 15:26:14 UTC
Created attachment 387344 [details, diff]
patch to test for /run/lvm directory during boot
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2014-10-25 16:56:02 UTC

*** This bug has been marked as a duplicate of bug 521960 ***
Comment 3 Fabio Rossi 2014-11-10 12:45:08 UTC
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
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2014-11-11 10:10:02 UTC

*** This bug has been marked as a duplicate of bug 521960 ***
Comment 5 Fabio Rossi 2014-11-12 22:24:55 UTC
(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