From: Patrik Jonsson <patrik@ucolick.org>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>,
linux-raid@vger.kernel.org
Subject: Re: Strange behaviour on "toy array"
Date: Mon, 16 May 2005 14:54:01 -0700 [thread overview]
Message-ID: <42891679.2090902@ucolick.org> (raw)
In-Reply-To: <20050516184049.90DDA11416@smtp.ucolick.org>
Ruth Ivimey-Cook wrote:
>
>Yes, I believe this interpretation is correct. Moreover, I've seen this happen
>"for real": when two drives died on my raid5 array while I was playing, I
>started to see some I/O errors, but only for things that hadn't just been
>accessed: recently accessed things were returned fine. As time went by, even
>those disappeared.
>
>I must admit, it's rather disconcerting, but it is a logical result of having a
>block cache.
>
>
This makes sense, however, I would have expected /proc/mdstat or
something telling me the array is DEAD. It seems "clean, degraded" is
not a proper description of a raid5 without any working drives... Or
would this not happen until I tried to write to it (which I haven't
gotten to yet)?
I must admit I don't remember seeing in the FAQ or anywhere what is
supposed to happen when you lose more than one drive. I sort of expected
to have the entire array go offline, but it seems it just limps along
like a normal faulty drive would do?
/Patrik
next parent reply other threads:[~2005-05-16 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050516184049.90DDA11416@smtp.ucolick.org>
2005-05-16 21:54 ` Patrik Jonsson [this message]
2005-05-17 2:28 ` Strange behaviour on "toy array" Guy
2005-05-17 6:04 ` Patrik Jonsson
2005-05-17 7:12 ` Patrik Jonsson
2005-05-17 8:41 ` David Greaves
2005-04-22 10:45 MD bug or me being stupid? Molle Bestefich
2005-05-12 8:55 ` Molle Bestefich
2005-05-13 2:55 ` Neil Brown
2005-05-15 18:10 ` Molle Bestefich
2005-05-15 18:22 ` Strange behaviour on "toy array" Patrik Jonsson
2005-05-15 20:09 ` David Greaves
2005-05-15 20:55 ` Patrik Jonsson
2005-05-15 22:13 ` Guy
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=42891679.2090902@ucolick.org \
--to=patrik@ucolick.org \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--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.