From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] *** ANNOUNCEMENT *** LVM 0.9.1 beta1 available at www.sistina.com
Date: Sat, 13 Jan 2001 17:26:38 -0600 [thread overview]
Message-ID: <3A60E42E.B7588C50@wrkhors.com> (raw)
In-Reply-To: 20010113163514.A24224@goliath.geekthing.com
> I wonder if this is why I lost all of my data last Thursday...
>
> vg w/ 2 pv's (hde1 & hdg1) and 3 lv's. Add a pv (hdc1) and
> reboot, and all of a sudden, even though the vg is still there,
> with 3 pv's and 3 lv's, the lv's won't even fsck (bad magic
> number in superblock -- doesn't even look like a filesystem was
> even there). I though maybe it had a problem w/ rearranging the
> pv's or something... How else could it completely lose track
> of my data?
>
> It was kernel 2.4.0 w/ the several-line vg_extend patch, and the 0.9
> tools...
you probably hadn't lost anything. one approach that usually
works is to:
vgexport vg0;
vgimport vg0 /first/disk /second/disk;
likely to get you back to where you were before the vgextend.
if vgimport doesn't like them anymore you can create a new lv,
vgextend it to the two devices and create new vg's w/ the same
allocations as the old ones (simple enough if they havn't been
extended too many times).
--
Steven Lembark 2930 W. Palmer St.
Chicago, IL 60647
lembark@wrkhors.com 800-762-1582
next prev parent reply other threads:[~2001-01-13 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 1:15 [linux-lvm] *** ANNOUNCEMENT *** LVM 0.9.1 beta1 available at www.sistina.com Heinz J. Mauelshagen
2001-01-13 16:04 ` Jan Niehusmann
2001-01-13 18:08 ` Holger Grothe
2001-01-13 18:30 ` Holger Grothe
2001-01-13 20:59 ` William L. Jones
2001-01-13 22:35 ` Rob Fugina
2001-01-13 23:26 ` Steven Lembark [this message]
2001-01-14 13:29 ` Jan Niehusmann
2001-01-14 14:17 ` Jan Niehusmann
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=3A60E42E.B7588C50@wrkhors.com \
--to=lembark@wrkhors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox