From: Richard Scobie <r.scobie@clear.net.nz>
To: Marc MERLIN <marc@merlins.org>
Cc: NeilBrown <neilb@suse.de>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: How to force rewrite of a smart detected bad block with raid5: checkarray?
Date: Thu, 20 Jan 2011 13:30:39 +1300 [thread overview]
Message-ID: <4D37822F.1080903@clear.net.nz> (raw)
In-Reply-To: <20110119205739.GI7117@merlins.org>
Marc MERLIN wrote:
> So, I went back and read man md, and md.txt in the kernel Documentation
> tree, but I could not find documentation on this:
> echo 3907029168 > sync_min
> echo 3907029170 > sync_max
>
> and as per my other post, it didn't work for me on 2.6.36
> (echo: write error: Invalid argument)
sync_max is mentioned in md.txt for 2.6.29.1 (currently running here):
This is a number of sectors at which point a resync/recovery
process will pause. When a resync is active, the value can
only ever be increased, never decreased. The value of 'max'
effectively disables the limit.
There is no mention of sync_min.
Regards,
Richard
next prev parent reply other threads:[~2011-01-20 0:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 18:36 How to force rewrite of a smart detected bad block with raid5: checkarray? Richard Scobie
2011-01-19 18:49 ` Marc MERLIN
2011-01-19 20:01 ` NeilBrown
2011-01-19 20:57 ` Marc MERLIN
2011-01-20 0:30 ` Richard Scobie [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-19 7:04 Marc MERLIN
2011-01-19 7:42 ` Mikael Abrahamsson
2011-01-19 9:41 ` NeilBrown
2011-01-19 17:31 ` Marc MERLIN
2011-01-19 20:58 ` NeilBrown
2011-01-19 21:03 ` Marc MERLIN
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=4D37822F.1080903@clear.net.nz \
--to=r.scobie@clear.net.nz \
--cc=linux-raid@vger.kernel.org \
--cc=marc@merlins.org \
--cc=neilb@suse.de \
/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).