Re: vgextend path to device should'n be allowed

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

 



On 12/20/2009 03:01 PM, Maurizio Marini Gmail wrote:
> IMHO, vgextend should check input and deny operation on a device instead of a
> volume group name; it should abort with an error,
...

> After extending whic /dev/sdc of 80G using wrong statement:
> vgextend /dev/mapper/VolGroup01 /dev/sdc

this works correctly with recent version of lvm2 (despite the strange syntax).

Please can you try to upgrade lvm2 (to RHEL/CentOS 5.4 version, the reported
version is from 5.3) and try it again (bu after restoring correct metadata)?

> Now, to fix it, can I issue:
> vgreduce --force  --removemissing VolGroup01

The best is revert metadata to version before the failed operation
(you pasted the correct version above:-) using vgcfgrestore command.

(The whole problem is stored "MISSING" flag in metadata, you can
also use last metadata backup, remove that flag manually and restore this
edited version.)

Milan
--
mbroz@redhat.com

_______________________________________________
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