From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] rescue data after hd crash
Date: Wed, 31 May 2006 23:31:54 +0200 [thread overview]
Message-ID: <20060531213154.GA2236@redhat.com> (raw)
In-Reply-To: <20060531124546.GF13142@dragonhold.org>
vgchange -ay --partial
On Wed, May 31, 2006 at 01:45:46PM +0100, Graham Wood wrote:
> On Wed, May 31, 2006 at 02:34:04PM +0200, chris wrote:
> > I have create a volume group with 4 250GByte harddisks with an ext3 file
> > system on the 1TB result.
> Stripe or concat?
>
> > now the third harddisk failed and the volume group is "dead" - obviously.
> The way you created the volume had no redundancy - therefore 25% of your data is gone, as
> well as the volume's "completeness".
>
> If you did a concat, then you (with playing) may be able to get some data back from the
> first 500GB of the volume - but I wouldn't want to rely on anything that came back from it.
> I'd suggest getting hold of 2 identical blank disks, and doing a binary (dd) copy of disks 1
> and 2 to them - and then work on them. You might be able to use vgcfg{backup,restore} to
> tell the system that this volume is actually only on 2 disks.... However, anything that
> references data > 500GB into the volume is almost definitely lost - because although you've
> got 750G-1TB, it's almost all going to be linked back into the section that you've lost.
>
> If you did a stripe, then you can forget getting any data back off it. You've lost every
> 4th block of whatever size you striped on. E.g. with a 64k stripe size, you'll have lost
> from 128k-192k, 384k-448k, etc. - and there's almost definitely going to be nothing
> salvagable from that.
>
> Graham
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
Storage Development 56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com PHONE +49 171 7803392
FAX +49 2626 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2006-05-31 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 12:34 [linux-lvm] rescue data after hd crash chris
2006-05-31 12:45 ` Graham Wood
2006-05-31 21:31 ` Heinz Mauelshagen [this message]
2006-05-31 22:39 ` chris
2006-05-31 23:25 ` Heinz Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 23:02 chris
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=20060531213154.GA2236@redhat.com \
--to=mauelshagen@redhat.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).