linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: Steve Cousins <steve.cousins@maine.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Care and feeding of RAID?
Date: Wed, 6 Sep 2006 09:16:09 +0200	[thread overview]
Message-ID: <20060906071609.GF17634@percy.comedia.it> (raw)
In-Reply-To: <44FDF08D.8000504@maine.edu>

On Tue, Sep 05, 2006 at 05:47:57PM -0400, Steve Cousins wrote:
>
>
>Luca Berra wrote:
>
>>On Tue, Sep 05, 2006 at 02:29:48PM -0400, Steve Cousins wrote:
>>
>>>
>>>
>>>Benjamin Schieder wrote:
>>>
>>>>On 05.09.2006 11:03:45, Steve Cousins wrote:
>>>>
>>>>>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? 
>>>>
>>>>
>>>>
>>>>Personally, I use this script from cron:
>>>>http://shellscripts.org/project/hdtest
>>
>>
>>nice race :)
>
>I'm not sure what you mean?

tmp="`mktemp`"
rm -f ${tmp}
touch ${tmp}

the last two lines are unneeded and can be tricked to overwrite
arbitrary filenames


>I tried smartctl -t short -d scsi /dev/sdb where /dev/sdb is a 250GB 
>SATA drive.

it is '-d ata'

>What command do you use for SATA drives?  The sourceforge page implies 
>that -d sata doesn't exist yet.  I'm using FC 5 with 2.6.17 kernel and 
>smartmontools version 5.33.  Do you have a sample configuration script 
>that you could show me?

# monitor two sata disks, show temperature in degrees,
# do a long test every sunday and a short every other day
# at 1am on sda and at 2am on sdb, YMMV
/dev/sda -d ata -a -R 194 -s (L/../../7|S/../../[123456])/01
/dev/sdb -d ata -a -R 194 -s (L/../../7|S/../../[123456])/02

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  parent reply	other threads:[~2006-09-06  7:16 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 [this message]
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=20060906071609.GF17634@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=steve.cousins@maine.edu \
    /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).