linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: David Rees <drees76@gmail.com>
Cc: dean gaudet <dean@arctic.org>, linux-raid@vger.kernel.org
Subject: Re: Resize on dirty array?
Date: Sat, 12 Aug 2006 08:36:11 +0400	[thread overview]
Message-ID: <44DD5ABB.1090804@wasp.net.au> (raw)
In-Reply-To: <72dbd3150608111905g43ac320bn1ab30cbe021a3f43@mail.gmail.com>

David Rees wrote:
>> > I personally prefer to do a long self-test once a week, a month seems
>> > like a lot of time for something to go wrong.
>>
>> unfortunately i found some drives (seagate 400 pata) had a rather 
>> negative
>> effect on performance while doing self-test.
> 
> Interesting that you noted negative performance, but I typically
> schedule the tests for off-hours anyway where performance isn't
> critical.

Personally I have every disk do a short test at 6am Monday-Saturday, and then they *all* (29 of 
them) do a long test every Sunday at 6am.

I figure having all disks do a long test at the same time rather than staggered is going to show up 
any pending issues with my PSU's also.

(Been doing this for nearly 2 years now and had it show up a couple of drives that were slowly 
growing defects. Nothing a dd if=/dev/zero of=/dev/sd(x) did not fix though)

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

  reply	other threads:[~2006-08-12  4:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  0:36 Resize on dirty array? James Peverill
2006-08-08  0:46 ` Neil Brown
2006-08-08 19:25   ` James Peverill
2006-08-09  4:09     ` Neil Brown
2006-08-09 11:28       ` James Peverill
2006-08-09 11:37         ` Martin Schröder
2006-08-09 13:05           ` Mark Hahn
2006-08-09 13:33             ` James Peverill
2006-08-09 21:17               ` David Greaves
2006-08-10 17:44               ` dean gaudet
2006-08-12  1:11                 ` David Rees
     [not found]                 ` <72dbd3150608111810m4e4a2e07r5ddcee2132dd6d9a@mail.gmail.com>
     [not found]                   ` <Pine.LNX.4.64.0608111813250.29322@twinlark.arctic.org>
2006-08-12  2:05                     ` David Rees
2006-08-12  4:36                       ` Brad Campbell [this message]
2006-08-13 16:02                       ` dean gaudet
2006-08-30  7:30                         ` dean gaudet
2006-08-11 17:34             ` John Stoffel
2006-08-09 14:56         ` Henrik Holst
2006-08-12  7:22         ` Tuomas Leikola
2006-08-28  4:55           ` Neil Brown
2006-08-28  6:36             ` Mario 'BitKoenig' Holbe

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=44DD5ABB.1090804@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=dean@arctic.org \
    --cc=drees76@gmail.com \
    --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).