From: Asdo <asdo@shiftmail.org>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Help on first dangerous scrub / suggestions
Date: Thu, 26 Nov 2009 15:13:19 +0100 [thread overview]
Message-ID: <4B0E8CFF.1080106@shiftmail.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0911261459330.14550@uplift.swm.pp.se>
Mikael Abrahamsson wrote:
> On Thu, 26 Nov 2009, Asdo wrote:
>
>> Now I am scared about initiating the first scrub because if it turns
>> out that 3 areas in different disks have bad sectors I think am gonna
>> lose the whole array.
>
> What kernel are you using?
>
> As of 2.6.15 or so, sending "repair" (or "resync", I don't remember
> exactly) to the md will read all data and if there is bad data, parity
> will be used to write to the bad sector (it shouldn't kick the disk).
>
> <http://linux-raid.osdl.org/index.php/RAID_Administration>
>
Kernel is ubuntu kernel 2.6.24 .
In the page you are linking I don't see mention of the fact that drives
won't be kicked with a "repair" or "check".
In fact regarding "check" this is written:
'check' just reads everything and doesn't trigger any writes unless a
read error is detected, in which case the normal read-error handing
kicks in.
"normal error handling" seems to suggest that if the read error is
uncorrectable the drive will be kicked. You don't think so?
Thank you
prev parent reply other threads:[~2009-11-26 14:13 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
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 [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=4B0E8CFF.1080106@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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).