From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Re-map disk sectors in userspace when rewriting after read errors
Date: Fri, 18 Sep 2009 18:44:00 +0100 [thread overview]
Message-ID: <4AB3C6E0.7010908@anonymous.org.uk> (raw)
In-Reply-To: <1253273738.9662.636.camel@kiste>
On 18/09/2009 12:35, Matthias Urlichs wrote:
[...]
> If you run a check on a degraded array and the check runs into errors it
> can't recover from, I assume that the disk will get kicked off and
> you'll have a nonfunctional array instead.
No, I don't think so - at least with RAID-1, md doesn't drop the array
on errors on the one remaining functional disc, on the grounds that some
data is better than none, but I don't know whether the array gets
switched to read-only or what the situation is with other RAID levels.
Cheers,
John.
next prev parent reply other threads:[~2009-09-18 17:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 6:23 Re-map disk sectors in userspace when rewriting after read errors Matthias Urlichs
2009-09-15 6:45 ` berk walker
2009-09-15 7:23 ` Matthias Urlichs
2009-09-15 7:13 ` Alex Butcher
2009-09-15 7:29 ` Matthias Urlichs
2009-09-15 7:37 ` Alex Butcher
2009-09-15 10:48 ` Matthias Urlichs
2009-09-16 9:41 ` Goswin von Brederlow
2009-09-16 13:13 ` Matthias Urlichs
2009-09-18 8:17 ` Majed B.
2009-09-18 8:28 ` Robin Hill
2009-09-18 9:57 ` Majed B.
2009-09-18 10:22 ` Robin Hill
2009-09-18 10:52 ` Majed B.
2009-09-18 11:15 ` Robin Hill
2009-09-18 11:35 ` Matthias Urlichs
2009-09-18 17:44 ` John Robinson [this message]
2009-09-18 18:02 ` Greg Freemyer
2009-09-18 20:13 ` Majed B.
2009-10-02 13:55 ` Bill Davidsen
2009-09-15 10:40 ` Majed B.
2009-09-15 10:52 ` Matthias Urlichs
2009-09-15 11:03 ` Majed B.
2009-09-15 17:02 ` Majed B.
2009-09-15 18:05 ` Matthias Urlichs
2009-09-15 18:14 ` Majed B.
2009-09-15 18:44 ` Matthias Urlichs
2009-09-16 9:31 ` Majed B.
2009-09-16 9:44 ` Matthias Urlichs
2009-09-16 9:52 ` Majed B.
2009-09-16 13:05 ` Alex Butcher
2009-09-16 10:00 ` Robin Hill
2009-09-16 10:07 ` Majed B.
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=4AB3C6E0.7010908@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.