From: Asdo <asdo@shiftmail.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Help on first dangerous scrub / suggestions
Date: Fri, 27 Nov 2009 19:11:31 +0100 [thread overview]
Message-ID: <4B101653.8040904@shiftmail.org> (raw)
In-Reply-To: <4B0FD689.9030904@shiftmail.org>
Asdo wrote:
> ....
> Without knowing this I will probably opt for your way: rsync data out,
> starting from the smallest and most important stuff...
> ...
I had another thought:
If I take the computer offline, boot with a livecd (one of the worst
messes here is that the root filesystem is also in that array), run the
raid6 array in READONLY MODE and maybe without spares, then I start a
check (scrub) ...
If drives are kicked I can probably reasseble --force the array and it's
like nothing happened, right?
Since it was mounted readonly I think it would be clean...
Only problem would be if 1 or more drives definitively die during the
procedure, but I hope this is unlikely...
If less than 3 drives die I can still reassemble --force, and take the
data out (at least SOME data, then if it degrades, reassemble again and
try to get out data from another location...)
Do you agree?
I am starting to think that during the procedure for taking the data out
and/or attempt first scrubbing the main problem are write accesses to
the array, because if rebuild starts on a spare and then fails again and
then there were writes in the middle... I think I end up doomed.
Probably even reassemble --force would refuse to work on me. What do you
think?
Thank you
next prev parent reply other threads:[~2009-11-27 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 12:14 Help on first dangerous scrub / suggestions Asdo
2009-11-26 12:22 ` Justin Piszcz
2009-11-26 14:06 ` Asdo
2009-11-26 14:38 ` Justin Piszcz
2009-11-26 19:02 ` Asdo
2009-11-26 20:55 ` Justin Piszcz
2009-11-27 13:39 ` Asdo
2009-11-27 18:11 ` Asdo [this message]
2009-11-27 21:08 ` Justin Piszcz
2009-11-27 21:21 ` Neil Brown
2009-12-02 10:15 ` Asdo
2009-11-26 14:03 ` Mikael Abrahamsson
2009-11-26 14:13 ` Asdo
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=4B101653.8040904@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=jpiszcz@lucidpixels.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).