From: Steve Cousins <steve.cousins@maine.edu>
To: Gordon Henderson <gordon@drogon.net>
Cc: Paul Waldo <pwaldo@waldoware.com>, linux-raid@vger.kernel.org
Subject: Re: Care and feeding of RAID?
Date: Tue, 05 Sep 2006 11:03:45 -0400 [thread overview]
Message-ID: <44FD91D1.7090501@maine.edu> (raw)
In-Reply-To: <Pine.LNX.4.56.0609051414310.17570@lion.drogon.net>
Gordon Henderson wrote:
>On Tue, 5 Sep 2006, Paul Waldo wrote:
>
>
>
>>Hi all,
>>
>>I have a RAID6 array and I wondering about care and feeding instructions :-)
>>
>>Here is what I currently do:
>> - daily incremental and weekly full backups to a separate machine
>> - run smartd tests (short once a day, long once a week)
>> - check the raid for bad blocks every week
>>
>>What else can I do make sure the array keeps humming? Thanks in advance!
>>
>>
>
>Stop fiddling with it :)
>
>I run similar stuff, but don't forget running mdadm in daemon mode to send
>you an email should a drive fail. I also check each device individually,
>rather than the array although I don't know the value of doing this over
>the SMART tests on modern drives though...
>
>
Would people be willing to list their setup? Including such things as
mdadm.conf file, crontab -l, plus scripts that they use to check the
smart data and the array, mdadm daemon parameters and anything else that
is relevant to checking and maintaining an array?
I'm running the mdmonitor script at startup and a sample mdadm.conf
(one of 3 machines) looks like:
MAILADDR cousins@limpet-gb.umeoce.maine.edu
ARRAY /dev/md0 level=raid5 num-devices=3
UUID=39d07542:f3c97e69:fbb63d9d:64a052d3
devices=/dev/sdb1,/dev/sdc1,/dev/sdd1
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?
Thanks,
Steve
next prev parent reply other threads:[~2006-09-05 15:03 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 [this message]
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
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=44FD91D1.7090501@maine.edu \
--to=steve.cousins@maine.edu \
--cc=gordon@drogon.net \
--cc=linux-raid@vger.kernel.org \
--cc=pwaldo@waldoware.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;
as well as URLs for NNTP newsgroup(s).