linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
To: John Rowe <rowe@excc.ex.ac.uk>, linux-raid@vger.kernel.org
Subject: Re: Slow reconstruction
Date: Wed, 29 Jun 2005 09:40:16 -0700	[thread overview]
Message-ID: <42C2CEF0.7030108@h3c.com> (raw)
In-Reply-To: <1120061430.21458.236.camel@volt>


John Rowe wrote:
> First, thanks to all the authors of software RAID, which works really
> well. 
> 
> I have just one problem(!) and as disks get bigger it gets worse:
> reconstruction takes a long time. At the moment I've just had a disk
> fail on a 5x250 GB RAID5 array and it's going to take eight days to
> recover. Is there anything I can do to speed things up?
> 
> FWIW, each disk is the master drive on an IDE card, two of the disks are
> shared with the RAID1 root partition and one of the 5 devices is a RAID0
> stripe. The system isn't doing anything else, it's just used for backup.

That is an astonishingly slow reconstruction time.

Have you looked at hdparm informational output on each of the drives?
dmesg, grepping for the hard drive initialization information?

With speeds like that, I suspect you don't have DMA enabled for some
reason. Maybe someone else has seen something more exactly matching
this, but when speeds are this off, that's what its been for me in the past.

Running hdparm -Tt /dev/hdXX can tell you what the disks can do
individually, I'd start there, and look at the hdparm -i (or -I?) output
to see what they were set at, and start tuning the interface.

Hopefully that turns something up quickly.

-Mike

  reply	other threads:[~2005-06-29 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 16:10 Slow reconstruction John Rowe
2005-06-29 16:40 ` Mike Hardy [this message]
2005-06-29 17:31   ` John Rowe
2005-06-29 17:46     ` seth vidal
2005-06-29 17:49       ` John Rowe
2005-06-29 17:49     ` KELEMEN Peter
2005-06-29 17:52       ` John Rowe
2005-06-29 18:00         ` KELEMEN Peter
2005-06-29 17:54     ` Tyler
2005-06-29 17:32 ` seth vidal

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=42C2CEF0.7030108@h3c.com \
    --to=mhardy@h3c.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rowe@excc.ex.ac.uk \
    /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).