Re: new multipath device mistakenly replaced another PV in existing volume group

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 19, 2017 at 02:53:19PM -0700, Neutron Sharc wrote:
> Please note that all these vol3_[0-3] are fresh, without any LVM
> metadata on them, as shown by pvscan::
> sudo pvscan --cache /dev/mapper/vol3_0
>   Incorrect metadata area header checksum on /dev/mapper/vol3_0 at offset 4096
>   Incorrect metadata area header checksum on /dev/mapper/vol3_0 at offset 4096
>   Incorrect metadata area header checksum on /dev/mapper/vol3_0 at offset 4096

That error indicates there is LVM metadata on them.

>   Found duplicate PV 9F6vU9NVBfEq1w3e04T5UreO6fDVPJNy: using
> /dev/mapper/vol1_3 not /dev/mapper/vol3_0

That error indicates it's the same LVM metadata on them.

Perhaps you're exporting the same data source on the back end via separate
devices, or have copied the data sources, or are using snapshots of them.

Dave

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/



[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux