From: NeilBrown <neilb@suse.de>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Peter Urbanec <linux-raid@urbanec.net>, linux-raid@vger.kernel.org
Subject: Re: RAID5 check does not read disk media
Date: Thu, 5 Apr 2012 09:45:55 +1000 [thread overview]
Message-ID: <20120405094555.7779a2a6@notabene.brown> (raw)
In-Reply-To: <CADNH=7HbC4M0obMV=nGNVWcH3vJT+nug725om+K7ocvk8=bPxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2514 bytes --]
On Wed, 4 Apr 2012 14:51:52 +0100 Mathias Burén <mathias.buren@gmail.com>
wrote:
> On 4 April 2012 14:23, Peter Urbanec <linux-raid@urbanec.net> wrote:
> > I'm running Gentoo kernel 3.3.0 with raid5 on four ICH7 AHCI connected
> > Seagate 2TB 7200RPM disks. I also have two WD 1TB Green disks in raid1 on a
> > Sil3114 with a JBOD (non-RAID) BIOS.
> >
> > When I attempt to do a scrub/check on the raid5, the check seems to proceed
> > without actually reading any data from the disks - the disk activity lights
> > do not even flicker.
> >
> > Looking at the speed at which the check completes confirms this:
> >
> > # cat /proc/sys/dev/raid/speed_limit_min
> > 10000
> > # cat /proc/sys/dev/raid/speed_limit_max
> > 4000000
> > # echo check > devices/virtual/block/md0/md/sync_action
> > # echo check > devices/virtual/block/md127/md/sync_action
> > ...
> > # cat /proc/mdstat
> > Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
> > md127 : active raid1 sdf1[1] sde1[0]
> > 976760384 blocks [2/2] [UU]
> > [>....................] check = 1.7% (17387072/976760384)
> > finish=380.7min speed=41994K/sec
> >
> > md0 : active raid5 sdb[1] sda[0] sdd[4] sdc[2]
> > 5860535808 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4]
> > [UUUU]
> > [==================>..] check = 93.9% (1835359616/1953511936)
> > finish=0.8min speed=2332893K/sec
> >
> >
> > raid1 runs at about 42MB/s as expected with two WD 1TB Green drives.
> > raid5 runs at well over 2GB/s - not really possible with four Seagate 2TB
> > 7200RPM drives.
> >
> > Any ideas on what may be going on there and how to fix it. Let me know
> > what/if more information may be needed.
> >
> > Thanks
> >
> > Peter Urbanec
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> FWIW I'm seeing this as well, kernel 3.3.1, but on RAID6. There's a
> message just a few days about this, but no link to a patch.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=c6d2e084c7411f61f2b446d94989e5aaf9879b0f
NeilBrown
>
> Mathias
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-04-04 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 13:23 RAID5 check does not read disk media Peter Urbanec
2012-04-04 13:51 ` Mathias Burén
2012-04-04 23:45 ` NeilBrown [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=20120405094555.7779a2a6@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@urbanec.net \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
/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).