From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: linux-raid@vger.kernel.org
Subject: Re: I am an idiot (power failure during chunk resize, no backup file)
Date: Thu, 4 Mar 2010 14:51:21 +0100 [thread overview]
Message-ID: <201003041451.21279.thomas.jarosch@intra2net.com> (raw)
In-Reply-To: <68c4f7e31003040437u233f8eb6q6d7351dba50578be@mail.gmail.com>
Alex,
On Thursday, 4. March 2010 13:37:54 you wrote:
> Yes I am using LVM. I'm not entirely sure how to go about messing
> with the mounting as you describe, I've never had to do it. Is this
> with the mount command? I do keep getting an error from lvm,
> "incorrect metadata area header checksum", with both chunk=64 and
> chunk=256 during the recreate.
Try to create a raw copy of those discs if your budget allows it
before you start fooling around. That way you won't damage
the real array any further and you can "experiment".
Your data should be worth it.
Cheers,
Thomas
prev parent reply other threads:[~2010-03-04 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 12:37 I am an idiot (power failure during chunk resize, no backup file) Alex Boag-Munroe
2010-03-04 13:51 ` Thomas Jarosch [this message]
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=201003041451.21279.thomas.jarosch@intra2net.com \
--to=thomas.jarosch@intra2net.com \
--cc=linux-raid@vger.kernel.org \
/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).