From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: Re: raid5+hotspare: request for recommended procedure
Date: Wed, 29 Sep 2010 14:38:23 +0200 [thread overview]
Message-ID: <4CA3333F.7060108@xunil.at> (raw)
In-Reply-To: <4CA32F61.3070802@seoss.co.uk>
Am 2010-09-29 14:21, schrieb Tim Small:
>> It should be repair, not check - check merely reads stuff, repair tries
>> to fix it.
>
> No it shouldn't, AFAIK - check will read from all sectors on all drives,
> and will trigger a rewrite on unreadable blocks (which is what the OP
> has).
I ran a repair on md3 now, currently I do it for md4.
kernel-docs say:
sync_action
a text file that can be used to monitor and control the rebuild
process. It contains one word which can be one of:
resync - redundancy is being recalculated after unclean
shutdown or creation
recover - a hot spare is being built to replace a
failed/missing device
idle - nothing is happening
check - A full check of redundancy was requested and is
happening. This reads all block and checks
them. A repair may also happen for some raid
levels.
repair - A full check and repair is happening. This is
similar to 'resync', but was requested by the
user, and the write-intent bitmap is NOT used to
optimise the process.
thanks, Stefan
prev parent reply other threads:[~2010-09-29 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 9:03 raid5+hotspare: request for recommended procedure Stefan G. Weichinger
2010-09-29 10:03 ` Tim Small
2010-09-29 10:06 ` Tim Small
2010-09-29 12:42 ` Stefan G. Weichinger
2010-09-29 14:25 ` Stefan G. Weichinger
2010-09-29 14:29 ` Jon Hardcastle
2010-09-29 15:08 ` Stefan G. Weichinger
2010-09-29 15:39 ` Jon Hardcastle
2010-09-30 9:50 ` Stefan G. Weichinger
2010-10-01 9:00 ` Stefan G. Weichinger
2010-10-01 9:59 ` Stefan G. Weichinger
2010-10-01 21:20 ` Stefan G. Weichinger
2010-09-29 12:01 ` Michael Tokarev
2010-09-29 12:21 ` Tim Small
2010-09-29 12:38 ` Stefan G. Weichinger [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=4CA3333F.7060108@xunil.at \
--to=lists@xunil.at \
--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).