From: "JaniD++" <djani22@dynamicweb.hu>
To: linux-raid@vger.kernel.org
Subject: Re: [PATCH md ] Better handling of readerrors with raid5.
Date: Mon, 19 Sep 2005 00:06:08 +0200 [thread overview]
Message-ID: <028d01c5bc9d$2f4f2310$0400a8c0@dcccs> (raw)
In-Reply-To: 432AF89C.3040407@h3c.com
Hello list!
I have found today one bad drive! (Maxtor 200G IDE)
I have also lost a lot of data thanks to that drive.
The problem:
The drive goes to crazy, and "can't remember", but dont say any error!
The RAID5 is still used that drive, and wasted the data what the system
writes to it...
I dont know is there any good trick to detect this error, but I have one
idea that can help some people on similar situation....
The job is simple:
Recover from RAID5 parity information, but don't write the data to any disk,
just verify the original data from drives, and reply the differences!
(same on raid1)
This helps to detect this light-bug drives.
And it is more useful, if the kernel can do that on the working array with
low priority...
I am lucky, because I have found easy this bad drive, that loses own MBR,
and 2 raid superblocks! :-) (raid0 on raid5)
Thanks
Janos
next prev parent reply other threads:[~2005-09-18 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050916125754.11044.patches@notabene>
2005-09-16 3:01 ` [PATCH md ] Better handling of readerrors with raid5 NeilBrown
2005-09-16 16:53 ` Mike Hardy
2005-09-16 21:39 ` Neil Brown
2005-09-18 22:06 ` JaniD++ [this message]
2005-09-21 0:15 ` Molle Bestefich
2005-09-21 9:14 ` Neil Brown
2005-09-21 15:07 ` Al Boldi
2005-10-23 3:57 ` Patrik Jonsson
2005-10-23 22:52 ` Neil Brown
2005-10-11 14:31 ` Mattias Wadenstein
2005-12-22 22:23 ` Stephan van Hienen
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='028d01c5bc9d$2f4f2310$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--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 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).