Not sure how I caused the below, but after a reboot I was unable to use my VG at all. I wiped it out and rebuilt it. Hopefully it does not happen again. Greg On 12/6/05, Greg Freemyer <greg.freemyer@gmail.com> wrote: > I have recently upgraded a test server from 2.4.x with LVM 1 to 2.6.13 > with LVM 2. > > I can mount my 3 LVs, but when I try to do basic lvm commands I get > "invalid lv in extent map". > > # pvscan > invalid lv in extent map > Couldn't fill logical volume maps. > invalid lv in extent map > Couldn't fill logical volume maps. > No matching physical volumes found > > # pvscan --version > LVM version: 2.01.14 (2005-08-04) > Library version: 1.01.04 (2005-08-02) > Driver version: 4.4.0 > > I did not run vgconvert manually, so I assume I still have LVM1 metadata. > > This is a test server, so none of the data in the LVs is important, > but I hope to be upgrading my live file server soon, so I would like > to figure out how to not lose any data. > > Thanks > Greg > -- > Greg Freemyer > The Norcross Group > Forensics for the 21st Century > -- Greg Freemyer The Norcross Group Forensics for the 21st Century _______________________________________________ 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/
