From: Steve Cousins <steve.cousins@maine.edu>
To: "Rev. Jeffrey Paul" <sneak@datavibe.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Care and feeding of RAID?
Date: Tue, 05 Sep 2006 14:35:06 -0400 [thread overview]
Message-ID: <44FDC35A.9060000@maine.edu> (raw)
In-Reply-To: <20060905175724.GK11132@datavibe.net>
Rev. Jeffrey Paul wrote:
> On Tue, Sep 05, 2006 at 11:03:45AM -0400, Steve Cousins wrote:
>
>>These are SATA drives and except for the one machine that has a 3Ware
>>8506 card in it I haven't been able to get SMART programs to do anything
>>with these drives. How do others deal with this?
>>
>
>
> I use the tw_cli program to check up on my 3ware stuff.
Hi Jeffrey,
Thanks. I use tw_cli too and I have scripted a check to see if it
degrades but this doesn't help with checking for disk problems before
they happen which SMART should help with. As it happens, smartctl works
with 3Ware SATA drives. It is my other SATA drives that I'm unable to
monitor.
Steve
> It took me quite a bit of time to figure that one out. I don't
> have any automated monitoring set up, but it'd be simple enough to
> script. I check on the array every so often and run a verify every few
> months to see if it kicks a disk out (it hasn't yet).
>
> 0 root@datavibe:~# tw_cli
> //datavibe> info
>
> Ctl Model Ports Drives Units NotOpt RRate VRate BBU
> ------------------------------------------------------------------------
> c0 8006-2LP 2 2 1 0 2 - -
>
> //datavibe> info c0
>
> Unit UnitType Status %Cmpl Stripe Size(GB) Cache AVerify IgnECC
> ------------------------------------------------------------------------------
> u0 RAID-1 OK - - 232.885 ON - -
>
> Port Status Unit Size Blocks Serial
> ---------------------------------------------------------------
> p0 OK u0 232.88 GB 488397168 WD-WMAL718611
> p1 OK u0 232.88 GB 488397168 WD-WMAL718619
> //datavibe>
>
> -j
>
--
______________________________________________________________________
Steve Cousins, Ocean Modeling Group Email: cousins@umit.maine.edu
Marine Sciences, 452 Aubert Hall http://rocky.umeoce.maine.edu
Univ. of Maine, Orono, ME 04469 Phone: (207) 581-4302
next prev parent reply other threads:[~2006-09-05 18:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 12:48 Care and feeding of RAID? Paul Waldo
2006-09-05 13:14 ` Benjamin Schieder
2006-09-05 16:56 ` Patrik Jonsson
2006-09-05 17:04 ` Gordon Henderson
2006-09-05 13:19 ` Gordon Henderson
2006-09-05 15:03 ` Steve Cousins
2006-09-05 15:41 ` Benjamin Schieder
2006-09-05 18:29 ` Steve Cousins
2006-09-05 20:57 ` Luca Berra
2006-09-06 7:12 ` Benjamin Schieder
2006-09-06 18:49 ` Luca Berra
2006-09-10 7:36 ` Benjamin Schieder
[not found] ` <44FDF08D.8000504@maine.edu>
2006-09-06 7:16 ` Luca Berra
2006-09-06 7:33 ` Mario 'BitKoenig' Holbe
2006-09-05 16:23 ` Mike Hardy
2006-09-05 17:02 ` Gordon Henderson
2006-09-05 17:46 ` Paul Waldo
2006-09-06 0:04 ` Gordon Henderson
2006-09-06 7:41 ` Mario 'BitKoenig' Holbe
2006-09-09 15:56 ` Nix
2006-09-05 17:09 ` Paul Waldo
2006-09-05 20:17 ` Richard Scobie
2006-09-05 17:57 ` Rev. Jeffrey Paul
2006-09-05 18:35 ` Steve Cousins [this message]
2006-09-05 17:39 ` Paul Waldo
2006-09-09 15:58 ` Nix
2006-09-10 5:23 ` 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=44FDC35A.9060000@maine.edu \
--to=steve.cousins@maine.edu \
--cc=linux-raid@vger.kernel.org \
--cc=sneak@datavibe.net \
/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).