From: "Erik Bågfors" <Erik.Bagfors@ardendo.se>
To: Linux LVM Mailinglist <linux-lvm@sistina.com>
Subject: [linux-lvm] Urgent, Please help LVM-krash
Date: Thu Dec 13 07:35:02 2001 [thread overview]
Message-ID: <1008250625.4350.5.camel@detrius> (raw)
Hi all!
Yesterday I krashed my lvm. This is the first time I'm having real
problems with it.
This is what happened.
I was going to add a new lv and used the lvcreate-command as usual.
This time I forgot the -n switch and when I realized that I hit ctrl-c..
BAD idea!
Now my vg is gone. I can't get it back whatever I try. Any help would
be VERY appreciated.
A vgscan just sais "no volume groups found" or something like that.
doing a pvdisplay on the pv's in my vg gives me that they should be in
"diskvg" (which is correct). I've tried doing vgcfgrestore from the
backups in /etc/lvmconf but that doesn't help. vgscan still doesn't
find it.
I looked at the HOWTO and found a program named uuid_fixer that looked
like it could solve the problem but it died with an "illegal
instruction" regardless of if I used the precompiled version or compiled
it myself.
This is on a mandrake 8.1-box with lvm, xfs, reiserfs and devfs so there
are alot of things to think about.
When doing stuff I did the following first:
reboot into single user, remount / rw, mount /proc, restore some
standar-stuff into /dev, and start devfsd
After that I tried vgcfgrestore, vgscan, uuid_fixer and just about
everything I could think or.
Please please please help me. Can anyone solve this. There are over 60
GB of stuff on this computer and it needs to work TODAY :(
/Erik
--
Erik Bågfors | http://www.ardendo.se/
Erik.Bagfors@ardendo.se | GSM +46 733 279 273
fingerprint: 6666 A85B 95D3 D26B 296B 6C60 4F32 2C0B 693D 6E32
next reply other threads:[~2001-12-13 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 7:35 Erik Bågfors [this message]
2001-12-17 5:22 ` [linux-lvm] Urgent, Please help LVM-krash Heinz J . Mauelshagen
2001-12-17 5:40 ` Erik Bågfors
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=1008250625.4350.5.camel@detrius \
--to=erik.bagfors@ardendo.se \
--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