[lvm-devel] master - scan: md metadata version 0.90 is at the end of disk

[Gang He]

Hello David,

Some feedback from our user is as below,

It still does not work out and ends up in the emergency console, although error messages are different now:
in journal (journalctl -xb):

Unit lvm2-pvscan at 259:0.service has finished starting up.
[...]
Dec 08 15:27:28 big lvmetad[560]: vg_lookup vgid 6zO4JX-piC2-OaCG-GptZ-MT2F-NH4J-jL6gNj name vghome found incomplete mapping uuid none name none
[...]
Dec 08 15:28:57 big systemd[1]: dev-vghome-data.device: Job dev-vghome-data.device/start timed out.
Dec 08 15:28:57 big systemd[1]: Timed out waiting for device dev-vghome-data.device.
-- Subject: Unit dev-vghome-data.device has failed
[...]

During boot following can be seen:
"A start job is running for dev-vghome-data.device (counting secs/1min 30s)"

This one fails and emergency console starts.

What can I provide additionally? 
Do you think his problem is related to these patches, or it is another problem?


Thanks
Gang

>>> On 2018/12/4 at 1:22, in message <20181203172221.GA6362 at redhat.com>, David
Teigland <teigland at redhat.com> wrote:
> On Sun, Dec 02, 2018 at 07:43:34PM -0700, Gang He wrote:
>> Hello David,
>> 
>> This patch can be used to fix this problem, or not?
>> https://www.redhat.com/archives/linux-lvm/2018-October/msg00049.html 
> 
> On the stable branch there are three recent commits to fix/improve
> md component detection.  I hope these will close any remaining gaps
> in this area, let me know how these work.
> 
> scan: md metadata version 0.90 is at the end of disk
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=0e42ebd6d4012d210084a9ccf8 
> d76f853726de3c
> 
> pvscan lvmetad: use full md filter when md 1.0 devices are present
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=a01e1fec0fe7c2fa61577c0e63 
> 6e907cde7279ea
> 
> pvscan lvmetad: use udev info to improve md component detection
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=a188b1e513ed5ca0f5f3702c82 
> 3490f5610d4495