From: David Liontooth <lionteeth@cogweb.net>
To: linux-raid@vger.kernel.org
Subject: Re: Raid0 rebuild slows to a crawl
Date: Fri, 13 Jan 2012 15:06:51 +0530 [thread overview]
Message-ID: <4F0FFB33.5090808@cogweb.net> (raw)
In-Reply-To: <4F0FEF00.7080300@uni-konstanz.de>
Much appreciated! I'll notify next-of-kin.
Cheers,
Dave
On 01/13/2012 02:14 PM, Kay Diederichs wrote:
> On 01/13/2012 09:01 AM, David Liontooth wrote:
>>
>> I'm trying to use a WD3200AAKX-001CA0 drive in a raid1 configuration
>> (Debian squeeze mdadm 3.1.4-1+8efb9d1), but adding it is unusably slow:
>>
>> # cat /proc/mdstat
>> Personalities : [raid1]
>> md1 : active raid1 sdb3[2] sda3[1]
>> 73015360 blocks [2/1] [_U]
>> [>....................] recovery = 0.0% (28928/73015360)
>> finish=2521.6min speed=482K/sec
>>
>> dmesg shows no errors:
>>
>> md: recovery of RAID array md0
>> md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
>> md: using maximum available idle IO bandwidth (but not more than 200000
>> KB/sec) for recovery.
>>
>> The drive itself doesn't seem to have a problem, though it's not
>> particularly fast:
>>
>> # hdparm -tT /dev/sdb
>>
>> /dev/sdb:
>> Timing cached reads: 11220 MB in 2.00 seconds = 5614.03 MB/sec
>> Timing buffered disk reads: 174 MB in 6.44 seconds = 27.01 MB/sec
>>
>> # smartctl -a /dev/sdb
>>
>> 5 Reallocated_Sector_Ct 0x0033 133 133 140 Pre-fail Always
>> FAILING_NOW 1265
>>
>> # hdparm -i /dev/sdb
>>
>> /dev/sdb:
>>
>> Model=WDC WD3200AAKX-001CA0, FwRev=15.01H15, SerialNo=WD-WCAYUEJ66523
>> Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
>> FmtGapReq }
>> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
>> BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=off
>> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=625142448
>> IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>> PIO modes: pio0 pio3 pio4
>> DMA modes: mdma0 mdma1 mdma2
>> UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
>> AdvancedPM=no WriteCache=enabled
>> Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
>>
>> * signifies the current active mode
>>
>> Is this a known problem? Only see it with this WD drive.
>>
>> Cheers,
>> Dave
>>
>
> Hi Dave,
>
> I'd say your drive is dying if its Reallocated_Sector_Ct is 1265.
> Dying drives often are really slow; they spend the time on trying to
> overcome error states.
>
> HTH,
> Kay
>
next prev parent reply other threads:[~2012-01-13 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 8:01 Raid0 rebuild slows to a crawl David Liontooth
2012-01-13 8:44 ` Kay Diederichs
2012-01-13 9:36 ` David Liontooth [this message]
2012-01-13 8:46 ` Raid1 " Robin Hill
2012-01-14 20:13 ` Raid0 " Stefan /*St0fF*/ Hübner
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=4F0FFB33.5090808@cogweb.net \
--to=lionteeth@cogweb.net \
--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).