From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Urgent, Please help LVM-krash
Date: Mon Dec 17 05:22:02 2001 [thread overview]
Message-ID: <20011217122223.A28720@sistina.com> (raw)
In-Reply-To: <1008250625.4350.5.camel@detrius>; from Erik.Bagfors@ardendo.se on Thu, Dec 13, 2001 at 02:37:04PM +0100
On Thu, Dec 13, 2001 at 02:37:04PM +0100, Erik Bågfors wrote:
> 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!
Erik,
that's actually starneg, because the tools intercept ctrl-c and the like :-(
>
> 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.
Did you run "pvcreate -ff" on all of your PVs belonging to diskvg *before*
you run vgcfgrestore on all of them? vgscan afetrwards.
>
> 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.
I think it was just the lack of pvcreate before vgcfgrestore.
>
> 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
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-12-17 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 7:35 [linux-lvm] Urgent, Please help LVM-krash Erik Bågfors
2001-12-17 5:22 ` Heinz J . Mauelshagen [this message]
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=20011217122223.A28720@sistina.com \
--to=mauelshagen@sistina.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.