Web lists-archives.com

Re: Unable to Access a Foreign Volume Group




Hi Jens,

my first shot would be setting the actual system id to 'zaphod1105820973' like described in the lvmsystemid man page. I'm not sure, how this uname or lvmlocal work, so I would try setting system_id_source to machineid or file.
First, look if /etc/machine-id matches. If not, put is may be in a /etc/lvm/system-id.

As this alters nothing in the LVM itself, this should not be harmful as a try.


Am 13.01.19 um 17:10 schrieb Jens Holzhäuser:
> Hello,
> 
> I have a buster/sid system with two volume groups that have made no
> issue for years.

[...]

> 
> # lvm systemid
>   system ID:
> # vgs -o systemid vg00
>   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local system ID.
>   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local system ID.
> # vgs --foreign -o +systemid
>   VG   #PV #LV #SN Attr   VSize   VFree   System ID
>   vg00   1   8   0 wz--n- 930.55g  20.00g zaphod1105820973
>   vg01   1   9   0 wz--n-  <1.50t 534.37g
> # vgchange --config 'local/extra_system_ids=["zaphod1105820973"]' --systemid "" vg00
>   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local system ID.
>   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local system ID.
> 
> 
> Any help is appreciated to get back acess to the VG, vgchange (and
> vgexport) seem to be ignoring it despite providing the extra system id.


[...]

> Thanks,
> 
> 
> 	Jens

Martin