Since the actual device /dev/vg0/logical0 actually gets created is it safe to assume that all LVM metadata is intact and correct and my problem is with the filesystem, not the lower level LVM?
Thanks,
Bernard Zolp
--- Begin Message ---I recently replaced a failing drive in my lvm1 volume group by doing a dd from the bad drive to a new drive. However after a few days I can no longer mount the logical volume. When I try to the mount the volume I get this output:
- To: linux-lvm@sistina.com
- Subject: vgck seg faulting
- From: "B. J. Zolp" <bjzolp@wisc.edu>
- Date: Mon, 05 Jan 2004 13:57:05 -0600
- Original-recipient: rfc822;bjzolp@wisc.edu
- Reply-to: linux-lvm@sistina.com
- Sender: linux-lvm-admin@sistina.com
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3.1) Gecko/20030425
mount: wrong fs type, bad option, bad superblock on /dev/vg0/logical0, or too many mounted file systems
I have a feeling that the superblock is corrupt.
I tried running vgck, but it seg faults after a point:
vgck -v vgck -- locking logical volume manager vgck -- finding all volume group(s) vgck -- checking volume group name "vg0" vgck -- checking existence of volume group "vg0" vgck -- reading volume group data for "vg0" from lvmtab vgck -- checking volume group consistency of "vg0" in lvmtab vgck -- VGDA of "vg0" in lvmtab is consistent vgck -- reading volume group data for "vg0" from physical volume(s) Segmentation fault (core dumped)
Can anyone help me get this mounted again?
thanks,
Bernard Zolp
_______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--- End Message ---
