From: Mike Fedyk <mfedyk@matchmail.com>
To: dean gaudet <dean-list-linux-raid@arctic.org>
Cc: Jason Lunz <lunz@falooley.org>, linux-raid@vger.kernel.org
Subject: Re: recovery of hosed raid5 array
Date: Sun, 26 Oct 2003 11:40:51 -0800 [thread overview]
Message-ID: <20031026194051.GA4511@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0310121034090.7866@twinlark.arctic.org>
On Sun, Oct 12, 2003 at 10:39:50AM -0700, dean gaudet wrote:
>
>
> On Sun, 12 Oct 2003, Jason Lunz wrote:
>
> > What was foolish was me provoking /dev/hde by asking it to report
> > diagnostics with smartctl at the same time the array was rebuilding
> > /dev/hdg. Even if something _was_ wrong with hde, it wouldn't have
> > helped me to find out then during the rebuild. Had the resync completed,
> > I'd have all my data now and one dead disk.
>
> querying SMART shouldn't cause this to happen -- but i've seen it occur
> with a promise controller and maxtor disks. i used to query the SMART
> data once a night just to have a log. then i switched it to once every 5
> minutes so i could graph the drive temperature... and when i went to once
> every 5 minutes the system became unstable. the kernel would randomly
> lose the ability to talk to a disk. the problem would go away after a
> reboot. i assume it was some sort of race condition.
1. Were they maxtor 160GB 8MB cache drives?
2. Is there any package that will take one drive in a raid1/5 array
offline, and run badblocks on it?
next prev parent reply other threads:[~2003-10-26 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 15:52 recovery of hosed raid5 array Jason Lunz
2003-10-11 18:59 ` linux-raid
2003-10-12 1:14 ` rob
2003-10-12 15:14 ` Jason Lunz
2003-10-12 17:39 ` dean gaudet
2003-10-12 18:04 ` Jason Lunz
2003-10-12 18:34 ` dean gaudet
2003-10-13 13:54 ` Dragan Simic
2003-10-13 17:00 ` dean gaudet
2003-10-26 19:40 ` Mike Fedyk [this message]
2003-10-26 19:48 ` Jason Lunz
2003-10-26 21:29 ` dean gaudet
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=20031026194051.GA4511@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=dean-list-linux-raid@arctic.org \
--cc=linux-raid@vger.kernel.org \
--cc=lunz@falooley.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).