From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] My VG is gone...
Date: Wed, 5 Sep 2001 15:41:56 -0500 [thread overview]
Message-ID: <20010905154156.A6046@sistina.com> (raw)
In-Reply-To: <B51F0C636E578A4E832D3958690CD73E0130BFFB@es04snlnt>; from jdiehl@sandia.gov on Wed, Sep 05, 2001 at 12:56:10PM -0600
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
On Wed, Sep 05, 2001 at 12:56:10PM -0600, Diehl, Jeffrey wrote:
> I will be formating 311Gb of hard drives today. These drives were 40% full.
> This is the second time that LVM has bitten me. The first time I tried to
> expand a VG, the VG was gone when the machine rebooted. Same thing this
> time. AND THERE IS APEARANTLY NO WAY TO RECOVER! It seems that all of the
> vg data is recorded in each member pv. So, why isn't there a utility to
> recover a vg in this situation? This is very fragile!
Did you try the uuid_fixer previously mentioned?
>
> -----Original Message-----
> From: Rasmus Wiman
> To: linux-lvm@sistina.com
> Sent: 9/5/2001 2:04 AM
> Subject: Re: [linux-lvm] My VG is gone...
>
> "Diehl, Jeffrey" <jdiehl@sandia.gov> skrev:
>
> > Any ideas about how to recover without losing my data. I need to get
> > going
> > soon, so if I haven't fixed it by late this week, I'm going to
> > reformat....
> > And lose several Gb of data.
>
> I have already reformated my hard disks, alas. I didn't have time to
> wait
> for a solution. But If someone would have helped me or suppllied code
> that
> fixed the problem, it could have beed the start of a Doctor LVM project.
> I
> think there should really be crash recover tools for any file system and
> LVM system since they all do crash some times.
>
>
> ---------------------
> Rasmus Wiman
> SAMI Labs
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
--
AJ Lewis
Sistina Software Inc. Voice: 612-638-0500
1313 5th St SE, Suite 111 Fax: 612-638-0500
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 60F3 160D C0D5 2C4B 751B 4FF9 6F67 E9BC 44CD DE95
-----Begin Obligatory Humorous Quote----------------------------------------
FATAL ERROR! SYSTEM HALTED! - Press any key to do nothing...
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-09-05 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 18:56 [linux-lvm] My VG is gone Diehl, Jeffrey
2001-09-05 20:41 ` AJ Lewis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-06 16:36 Diehl, Jeffrey
2001-09-04 20:51 Diehl, Jeffrey
2001-09-05 8:04 ` Rasmus Wiman
2001-08-31 5:15 Rasmus Wiman
2001-08-31 7:41 ` Rasmus Wiman
2001-08-31 9:22 ` Joe Thornber
2001-09-02 18:07 ` Rasmus Wiman
2001-09-02 19:03 ` svetljo
2001-09-04 12:43 ` AJ Lewis
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=20010905154156.A6046@sistina.com \
--to=lewis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox