From: "B. J. Zolp" <bjzolp@wisc.edu>
To: linux-lvm@redhat.com
Subject: [Fwd: [linux-lvm] vgck seg faulting]
Date: Thu Jan 8 10:41:03 2004 [thread overview]
Message-ID: <3FFCF4B4.6000004@wisc.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
Does anyone beleive that running a tool such as gpart or rescuept would
help recover the missing superblock and allow me to mount the logical
volume?
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
[-- Attachment #2: [linux-lvm] vgck seg faulting --]
[-- Type: message/rfc822, Size: 4967 bytes --]
From: "B. J. Zolp" <bjzolp@wisc.edu>
To: linux-lvm@sistina.com
Subject: [linux-lvm] vgck seg faulting
Date: Mon, 05 Jan 2004 13:57:05 -0600
Message-ID: <3FF9C191.5090006@wisc.edu>
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:
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/
reply other threads:[~2004-01-08 10:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FFCF4B4.6000004@wisc.edu \
--to=bjzolp@wisc.edu \
--cc=linux-lvm@redhat.com \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.