From: Daniel Santos <daniel.dlds@gmail.com>
To: linux-raid@vger.kernel.org
Subject: raid5 post mortem analisys
Date: Fri, 21 Sep 2007 17:25:19 +0100 [thread overview]
Message-ID: <46F3F06F.1060008@gmail.com> (raw)
Hello,
I had a raid 5 array with 3 drives. (on a USB 2.0 bus :)). After some
time, on drive failed. After some more time another drive failed and the
array stopped running.
I know that the usage pattern from the first failure to the second was
read-only, i.e as a user only reads were performed.
I also know that the cause of the drive's failures was that they just
dissapeared from the USB bus (probably from a bug in the hard drive's
enclosure's USB to IDE bridge)
I trashed the array anyway, but since I am new to linux md devices, I
was wishing that you could help me understand if there was any
possibility of getting it back up assuming that there was no data
corruption.
I run kernel 2.6.17 on a debian system and use mdadm for controlling the
array from user space.
Daniel Santos
next reply other threads:[~2007-09-21 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 16:25 Daniel Santos [this message]
2007-09-22 13:52 ` raid5 post mortem analisys Bill Davidsen
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=46F3F06F.1060008@gmail.com \
--to=daniel.dlds@gmail.com \
--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).