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

[linux-lvm] LVs corrupted after pvresize



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yohoo!

I'm currently in big troubles :-(
What happened?

I have a single VG running on three RAID arrays.

I resized one of these RAID arrays for additional 250GB. After this was
done I needed to reboot for the kernel to pick up the new size.
Then I went into fdisk, deleted the 8e-LVM partition and re-created a
new one with the same starting sector but a later end sector.
Again, for the kernel to pick up the new partition table I rebooted.

After the reboot my VG was inaccessible because it complained about a
missing PV.
I checked
http://www.novell.com/coolsolutions/appnote/19386.html#DiskPermanentlyRemoved
Symptom2, Solution2.

vgcfgrestore showed the same error: "Couldn't find device with uuid ..."

So I re-created th PV with "pvcreate --uuid [...] /dev/sdd1.

vgscan and I had the new size and a running VG showing all my LVs. :)

Unfortunately ALL my LVs on the /dev/sdd1 PV are severely corrupted- the
complain about missing partition tables, fsck.ext2 prints thousands of
errors and so on.

I tried to reduce the PV again, but the LVs remain corrupted.

I don't expect my data to be recoverable- but I want to know what I did
wrong.

Though, if you can recover my LVs it would be fine ;-)


Any ideas?


Christian


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFI96130XNIYlAXmzsRAqMGAKDK13dabQD/LFGl460R410PQlNFCQCgt7ZT
iVCXd/QCUoSQIdfTaODAbPU=
=XMWS
-----END PGP SIGNATURE-----


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