From: Marc MERLIN <marc_lvm@merlins.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgchange -a y /dev/System fails
Date: Fri Feb 1 15:10:02 2002 [thread overview]
Message-ID: <20020201210928.GO8651@merlins.org> (raw)
In-Reply-To: <20020131121417.A9764@sistina.com>
On Thu, Jan 31, 2002 at 12:14:17PM +0100, Heinz J . Mauelshagen wrote:
> > -> My BigAssLVMRaid VG is gone :-(
> >
> > Did I just lose my data?
>
> If you really tried all your metadata backups unsuccessfully, I am afraid
> so :-(
I tried other ones, but every time, I'm getting:
vgcfgrestore -- VGDA for "BigAssLVMRaid" successfully restored to physical
volume "/dev/rd/disc0/part7"
vgcfgrestore -- you may not have an actual backup of restored volume group
"BigAssLVMRaid"
Am I supposed to give a special flag to vgcfgrestore, or maybe pvcreate?
(I did not use the default physicalextentsize)
As a reminder, I am currently running this command:
FILE=/etc/lvmconf/BigAssLVMRaid.conf.2.old; vgcfgrestore -f $FILE -n BigAssLVMRaid -ll; read a; pvcreate -yff `cat /tmp/partlist`; for pv in `cat /tmp/partlist `; do vgcfgrestore -f $FILE -n BigAssLVMRaid $pv; done; vgscan
Short of all this, can I re-create the VG the same way I did the first
time, and hope to get my filesytem again if I recreate the same LVs?
(like I can do with software raid)
This VG was working fine before I restored the other one (active and all)
> Some users reported snapshot problems with the recent 2.4.x kernels. They
> are not 100% reliable due to VM issues being sorted out by the kernel
> community hopefully which will hopefully be integrated in 2.4.18.
Ok. I guess I'll know to steer clear from snapshots in the meantime, but if
LVM doesn't even allow me to recover a VG that hasn't been overwriten with
random data, I don't know how much data I'm willing to trust to it...
Either way, thanks for your help.
Marc
--
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
next prev parent reply other threads:[~2002-02-01 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 17:36 [linux-lvm] vgchange -a y /dev/System fails Marc MERLIN
2002-01-28 3:47 ` Heinz J . Mauelshagen
2002-01-29 15:58 ` Marc MERLIN
2002-01-30 6:17 ` Heinz J . Mauelshagen
2002-01-30 21:04 ` Marc MERLIN
2002-01-31 5:19 ` Heinz J . Mauelshagen
2002-02-01 15:10 ` Marc MERLIN [this message]
2002-02-11 13:01 ` Marc MERLIN
2002-01-29 18:25 ` Adrian Head
2002-01-30 6:20 ` Heinz J . Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 16:02 Marc MERLIN
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=20020201210928.GO8651@merlins.org \
--to=marc_lvm@merlins.org \
--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.