[linux-lvm] LVM says physical volumes are missing, but they are not

[Phillip Susi]

I upgraded last night to Ubuntu 16.04, and LVM has ( even when booting
back into 15.10 ) decided that two of my three physical volumes are
missing, but they are not:

***@faldara:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/md0 faldara lvm2 a-m 101.91g 58.91g
/dev/md1 faldara lvm2 a-m 1.69t 264.86g
/dev/sdb1 faldara lvm2 a-- 1.82t 1.81t
***@faldara:~$ sudo vgchange -ay
Refusing activation of partial LV faldara/Music. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/Videos. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/swap. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/trusty-old. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/vivid. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/pool0. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/xenial. Use
'--activationmode partial' to override.
6 logical volume(s) in volume group "faldara" now active

If I use --activationmode partial, then all volumes are correctly
mapped, with no missing extents:

***@faldara:~$ sudo dmsetup table faldara-vivid
0 44040192 linear 9:1 2468358144
44040192 24969216 linear 9:1 2996840448
69009408 14876672 linear 8:17 2048
***@faldara:~$ sudo dmsetup table faldara-xenial
0 83886080 linear 9:0 98304

How can it claim the pvs are missing, and then go ahead and use them?
Is there a way to manually clear the missing flag from the pv?

[Zdenek Kabelac]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I upgraded last night to Ubuntu 16.04, and LVM has ( even when booting
back into 15.10 ) decided that two of my three physical volumes are
PV VG Fmt Attr PSize PFree
/dev/md0 faldara lvm2 a-m 101.91g 58.91g
/dev/md1 faldara lvm2 a-m 1.69t 264.86g
/dev/sdb1 faldara lvm2 a-- 1.82t 1.81t
Refusing activation of partial LV faldara/Music. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/Videos. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/swap. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/trusty-old. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/vivid. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/pool0. Use
'--activationmode partial' to override.
Refusing activation of partial LV faldara/xenial. Use
'--activationmode partial' to override.
6 logical volume(s) in volume group "faldara" now active
If I use --activationmode partial, then all volumes are correctly

Hi

Please provide full 'vgchage -ay -vvvv' trace of such activation command.

Also specify which version of lvm2 is in use by your distro.

Regards

Zdenek

[Phillip Susi]

Post by Zdenek Kabelac
Hi
Please provide full 'vgchage -ay -vvvv' trace of such activation command.
Also specify which version of lvm2 is in use by your distro.

2.02.133-1ubuntu10. I ended up fixing it by doing a vgcfgbackup,
manually editing the text file to remove the MISSING flags, and then
vgcfgrestore. My guess is that when I initially installed 16.04, I
forgot to install mdadm, and so the init scripts must have forced a
partial activation without the raid pvs present, and that set the
MISSING flag on those pvs in the metadata on the remaining drive.
Once set, there appears to be no way to remedy this other than what I
ended up doing. It seems to me that having the volume actually
present should override the MISSING flag in the metadata, or at least
you should be able to clear the flag with pvchange.

[Zdenek Kabelac]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Post by Zdenek Kabelac
Hi
Please provide full 'vgchage -ay -vvvv' trace of such activation command.
Also specify which version of lvm2 is in use by your distro.

2.02.133-1ubuntu10. I ended up fixing it by doing a vgcfgbackup,
manually editing the text file to remove the MISSING flags, and then

Hi

Instead of doing manual 'edit' you should have used:

vgextend --restoremissing /dev/your_restored_pv

If you do a manual edit - there is quite large probability the restored
device will cause data inconsistencies for raid/mirrors....


(And complementary command if you would have wanted to drop a missing PV:
vgreduce --removemissing)


Regards

Zdenek