From: Bill Davidsen <davidsen@tmr.com>
To: Andy Smith <andy@lug.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Checking the sanity of SATA disks
Date: Mon, 07 Nov 2005 14:22:07 -0500 [thread overview]
Message-ID: <436FA95F.4030007@tmr.com> (raw)
In-Reply-To: <20051004142913.GK6594@strugglers.net>
Andy Smith wrote:
>Hello,
>
>I have a home fileserver with 4 SATA disks in a RAID 5. As I am
>sure you are aware, SATA devices in Linux currently cannot be
>queried for SMART info, so I can't do SMART health checks of these
>devices.
>
>Also there is still the tendency for Linux Software RAID to kick
>devices out of the array as soon as there is any error on them.
>
>I really don't want to be in the situation where a drive dies, I fit
>a new one, and during the resync another device is kicked out
>because of spontaneously finding a bad sector.
>
>I tried simply doing a
>
> dd if=/dev/sd[abcd] of=/dev/null
>
>To check each disk in a very unsubtle fashion, but it drives the
>load average on the machine way way up (like to 20+) and makes it
>very unresponsive (wait several minutes for a keypress to be
>acknowledged), even if I run it under nice -n 19.
>
You (a) want to use larger buffers, and (b) a program which uses
O_DIRECT for i/o. I had a news server which was running 28 aps until I
started using dd, then it dropped to 3 aps. Usinf O_DIRECT there is no
measurable slowdown (and no buffer contention).
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2005-11-07 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 14:29 Checking the sanity of SATA disks Andy Smith
2005-10-04 14:42 ` Molle Bestefich
2005-10-04 14:56 ` Andy Smith
2005-10-04 15:02 ` Molle Bestefich
2005-10-04 15:59 ` Patrik Jonsson
2005-10-04 17:32 ` Dan Stromberg
2005-10-05 11:08 ` Andy Smith
2005-10-09 15:21 ` Mark Hahn
2005-11-07 19:22 ` Bill Davidsen [this message]
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=436FA95F.4030007@tmr.com \
--to=davidsen@tmr.com \
--cc=andy@lug.org.uk \
--cc=linux-raid@vger.kernel.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).