From: Krzysztof Adamski <k@adamski.org>
To: linux-raid@vger.kernel.org
Subject: Raid6 rebuild question
Date: Thu, 02 Feb 2012 16:16:42 -0500 [thread overview]
Message-ID: <1328217402.9581.84.camel@oxygen.netxsys.com> (raw)
I changed a drive in a Raid 6 array and while I'm watching the rebuild,
this is what I see from the atop command:
DSK | sdo | busy 99% | read 397/s | write 0/s | avio 2 ms |
DSK | sdm | busy 64% | read 0/s | write 310/s | avio 2 ms |
DSK | sdk | busy 62% | read 577/s | write 0/s | avio 1 ms |
DSK | sdp | busy 60% | read 579/s | write 0/s | avio 1 ms |
DSK | sdi | busy 60% | read 584/s | write 0/s | avio 1 ms |
DSK | sdn | busy 60% | read 578/s | write 0/s | avio 1 ms |
DSK | sdj | busy 59% | read 587/s | write 0/s | avio 1 ms |
DSK | sdl | busy 59% | read 580/s | write 0/s | avio 1 ms |
sdm is the new drive, all drives are identical and connected to the same
LSI controller. Is this normal or sdo is having problems?
md2 : active raid6 sdm3[8] sdl3[0] sdo3[6] sdj3[5] sdi3[4] sdp3[3] sdk3[2] sdn3[1]
8777658240 blocks level 6, 64k chunk, algorithm 2 [8/7] [UUUUUUU_]
[============>........] recovery = 63.3% (926139636/1462943040) finish=190.9min speed=46850K/sec
bitmap: 0/11 pages [0KB], 65536KB chunk
reply other threads:[~2012-02-02 21:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1328217402.9581.84.camel@oxygen.netxsys.com \
--to=k@adamski.org \
--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).