From: Stephan von Krawczynski <skraw@ithnet.com>
To: "David Rees" <dbr@greenhydrant.com>
Cc: mdresser_l@windsormachine.com, linux-kernel@vger.kernel.org
Subject: Re: 3ware and two drive hardware raid1
Date: Fri, 13 Jun 2003 19:33:09 +0200 [thread overview]
Message-ID: <20030613193309.2d538c31.skraw@ithnet.com> (raw)
In-Reply-To: <3570.66.75.244.69.1055521381.squirrel@www.greenhydrant.com>
On Fri, 13 Jun 2003 09:23:01 -0700 (PDT)
"David Rees" <dbr@greenhydrant.com> wrote:
> Mike Dresser said:
> >
> > I'm heading out there today to take a look at the machine and see what
> > happened. I'm rather dissappointed in the 3ware utility, it alternately
> > claims both drives are ok(./tw_cli info c1 is different from ./tw_cli
> > info c1 u0)
> >
> > I was relying on that too much, and ignored the possiblity of two drive
> > failure. Looks like both drives would have failed at exactly the same
> > time, which sounds like a power spike.
>
> On the 3ware boxes I use, I setup the 3DM utility to run weekly scans of
> the unit to look for badblocks, do you do the same thing? I've had the
> scan turn up bad disks before.
>
> -Dave
I can confirm that the 3dm daemon is very handy. Especially the media scan is
highly recommended, as it finds problems on areas where there is no production
data yet. So there always is a good chance for replacement before actual failure.
Regards,
Stephan
next prev parent reply other threads:[~2003-06-13 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 15:56 3ware and two drive hardware raid1 Mike Dresser
2003-06-13 9:03 ` Alan Cox
2003-06-13 14:20 ` Mike Dresser
2003-06-13 16:23 ` David Rees
2003-06-13 17:33 ` Stephan von Krawczynski [this message]
2003-06-13 18:13 ` Mike Dresser
2003-06-13 20:46 ` David Rees
2003-06-13 21:00 ` Mike Dresser
2003-06-13 18:11 ` Mike Dresser
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=20030613193309.2d538c31.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=dbr@greenhydrant.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdresser_l@windsormachine.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