From: David Greaves <david@dgreaves.com>
To: Chris Worley <worleys@gmail.com>
Cc: Maurice Hilarius <maurice@harddata.com>, linux-raid@vger.kernel.org
Subject: Re: Interesting article
Date: Thu, 15 Jan 2009 11:09:00 +0000 [thread overview]
Message-ID: <496F194C.2050002@dgreaves.com> (raw)
In-Reply-To: <f3177b9e0901141455i460f09cs69e38e24842e9c62@mail.gmail.com>
Chris Worley wrote:
> On Wed, Jan 14, 2009 at 1:02 PM, Maurice Hilarius <maurice@harddata.com> wrote:
>> I read this today:
>> http://blogs.zdnet.com/storage/?p=162
>>
>> Would anyone who knows enough about this care to comment?
>
> We need disks continuously scanned in spare cycles, and offline the
> drives (or remap the sectors) as soon as an error is found.
>
> Also, when rebuilding an array, don't stop due to a read failure.
> mark the sector as bad and complete the rebuild.
>
> Waiting for a drive to fail has been too late to recover the array, in
> my experience.
Agreed - and I think another huge gap is that when you lose a block you really
should be able to find out what file was affected. Doable on ext3 but not
(AFAIK) xfs.
Though that is a filesystem issue, not a RAID issue.
David
next prev parent reply other threads:[~2009-01-15 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 20:02 Interesting article Maurice Hilarius
2009-01-14 22:55 ` Chris Worley
2009-01-15 11:09 ` David Greaves [this message]
2009-01-15 22:13 ` Michal Soltys
2009-01-15 22:31 ` David Greaves
2009-01-16 7:12 ` Peter Rabbitson
2009-01-15 0:57 ` Guy Watkins
2009-01-15 9:09 ` Jon Hardcastle
2009-01-15 11:51 ` RAID5 recoverability - Was: " Matti Aarnio
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=496F194C.2050002@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=maurice@harddata.com \
--cc=worleys@gmail.com \
/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).