From: Pierre Ossman <pierre-list@ossman.eu>
To: neilb@suse.de
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Raid not shutting down when disks are lost?
Date: Sat, 21 Nov 2009 17:03:55 +0100 [thread overview]
Message-ID: <20091121170355.7540d169@mjolnir.ossman.eu> (raw)
In-Reply-To: <20091008163952.679572b5@mjolnir.ossman.eu>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
Neil?
On Thu, 8 Oct 2009 16:39:52 +0200
Pierre Ossman <pierre-list@ossman.eu> wrote:
> Today one RAID6 array I manage decided to lose four out of eight disks.
> Oddly enough, the array did not shut down but instead I got
> intermittent read and writer errors from the filesystem.
>
> It's been some time since I had a failure of this magnitude, but I seem
> to recall that once the array lost too many disks, it would shut down
> and refuse to write a single byte. The nice effect of this was that if
> it was a temporary error, you could just reboot and the array would
> start nicely (albeit in degraded mode).
>
> Has something changed? Is this perhaps an effect of using RAID6 (I used
> to run RAID5 arrays)? Or was I simply lucky the previous instances I've
> had?
>
> Related, it would be nice if you could control how it handles lost
> disks. E.g. I'd like it to go read-only when it goes in to fully
> degraded mode. In case the last disk lost was only a temporary glitch,
> the array could be made to recover without a lengthy resync.
>
> Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by FRA, a
Swedish intelligence agency. Make sure your server uses
encryption for SMTP traffic and consider using PGP for
end-to-end encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-21 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 14:39 Pierre Ossman
2009-11-21 16:03 ` Pierre Ossman [this message]
2009-11-21 19:21 ` Dan Williams
2009-11-21 19:36 ` Pierre Ossman
2009-11-21 20:58 ` Dan Williams
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=20091121170355.7540d169@mjolnir.ossman.eu \
--to=pierre-list@ossman.eu \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®