Bug#315339: update to lvm2 2.02.05-1 renders striped vg unusable
Bastian Blank
waldi at debian.org
Sat Jun 10 20:05:04 UTC 2006
On Sat, Jun 10, 2006 at 11:53:41AM +0200, Tjeerd Pinkert wrote:
> I would say it looked like (i can get you this but than I have to render
> my system 'unusable' first):
> # vgdisplay datavolume
> LV backup: inconsistent LE count 547 != 1094
> Internal error: LV segments corrupted in backup.
> Volume group "datavolume" doesn't exist
>
> now it says (with 2.01.04-5):
> # vgdisplay datavolume
> --- Volume group ---
> VG Name datavolume
> System ID muziekje1075727894
> Format lvm1
> VG Access read/write
> VG Status resizable
> MAX LV 256
> Cur LV 1
> Open LV 1
> Max PV 256
> Cur PV 2
> Act PV 2
> VG Size 34.19 GB
> PE Size 32.00 MB
> Total PE 1094
> Alloc PE / Size 1094 / 34.19 GB
> Free PE / Size 0 / 0
> VG UUID elbhhh-3TS6-Qhju-ie78-13sj-rGG4-euaOEr
You have a broken lvm1 metadata block on one PV. Use vgcfgrestore to
rewrite it.
Bastian
--
You! What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20060610/b4aa464e/attachment.pgp
More information about the pkg-lvm-maintainers
mailing list