I hosed my vg yesterday with a failed pvmove. Now on
boot, I see lots error messages in the system logs to
the tune of:
device-mapper: mirror log: unrecognised sync
argument to mirror log: 2
device-mapper: ioctl: error adding target to table
device-mapper: table: device 254:0 too small for
target
one for each of my logical volumes. mke2fs on one of
these volumes reports these errors:
mke2fs 1.39 (29-May-2006)
mke2fs: Device size reported to be zero. Invalid
partition specified, or partition table
wasn't reread after running fdisk, due to
a modified partition being busy and in use.
You may need to reboot to re-read your
partition table.
I am using debian unstable, with the following three
kernels:
vmlinuz-2.6.17-1-vserver-686
vmlinuz-2.6.18-3-vserver-686
vmlinuz-2.6.17-1-686
-lvm version 2.02.06-3
-lvm-common 1.5.20
Any clues to how I can repair my volume group?
Thanks,
-Martin
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.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/
