All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Brassow <jbrassow@redhat.com>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: Re: Scrubbing "check" not working for RAID10 in 3.10-rc1+
Date: Mon, 15 Jul 2013 10:40:49 -0500	[thread overview]
Message-ID: <1373902849.31715.4.camel@f16> (raw)
In-Reply-To: <1372141160.2016.0.camel@f16>

[-- Attachment #1: Type: text/plain, Size: 2786 bytes --]

Neil,

You will need to change 'devices' to suite your needs.  I can run this
test with RAID 1/4/5/6 and it works, but it fails with RAID10 since
10-rc1.

thanks,
 brassow

example output:
[~]# ./md.sh 1
mdadm: /dev/sda1 appears to be part of a raid array:
    level=raid5 devices=4 ctime=Sat Jul 13 14:52:49 2013
mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device.  If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
mdadm: /dev/sdb1 appears to be part of a raid array:
    level=raid5 devices=4 ctime=Sat Jul 13 14:52:49 2013
mdadm: /dev/sdc1 appears to be part of a raid array:
    level=raid5 devices=4 ctime=Sat Jul 13 14:52:49 2013
mdadm: /dev/sdd1 appears to be part of a raid array:
    level=raid5 devices=4 ctime=Sat Jul 13 14:52:49 2013
mdadm: largest drive (/dev/sda1) exceeds size (102400K) by more than 1%
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
        Waiting for resync to complete
        Waiting for resync to complete
        Waiting for resync to complete
        Waiting for resync to complete
RAID1 mismatch count after creation     : 0
mdadm: stopped /dev/md0
Writing garbage to one of the MD devices...
mdadm: /dev/md0 has been started with 4 drives.
RAID1 mismatch count after reactivation : 0
        Waiting for check to complete
        Waiting for check to complete
        Waiting for check to complete
RAID1 mismatch count after data-check   : 61440
mdadm: stopped /dev/md0


[~]# ./md.sh 10
mdadm: /dev/sda1 appears to be part of a raid array:
    level=raid1 devices=4 ctime=Mon Jul 15 10:30:44 2013
mdadm: /dev/sdb1 appears to be part of a raid array:
    level=raid1 devices=4 ctime=Mon Jul 15 10:30:44 2013
mdadm: /dev/sdc1 appears to be part of a raid array:
    level=raid1 devices=4 ctime=Mon Jul 15 10:30:44 2013
mdadm: /dev/sdd1 appears to be part of a raid array:
    level=raid1 devices=4 ctime=Mon Jul 15 10:30:44 2013
mdadm: largest drive (/dev/sda1) exceeds size (102400K) by more than 1%
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
        Waiting for resync to complete
        Waiting for resync to complete
        Waiting for resync to complete
RAID10 mismatch count after creation     : 0
mdadm: stopped /dev/md0
Writing garbage to one of the MD devices...
mdadm: /dev/md0 has been started with 4 drives.
RAID10 mismatch count after reactivation : 0
        Waiting for check to complete
        Waiting for check to complete
        Waiting for check to complete
RAID10 mismatch count after data-check   : 0
mdadm: stopped /dev/md0
***** mismatch_cnt should not be zero !!!!!!


[-- Attachment #2: md.sh --]
[-- Type: application/x-shellscript, Size: 1742 bytes --]

      parent reply	other threads:[~2013-07-15 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25  6:19 Scrubbing "check" not working for RAID10 in 3.10-rc1+ Jonathan Brassow
2013-06-25  6:32 ` NeilBrown
2013-07-15 15:35   ` Brassow Jonathan
2013-07-16  7:01     ` NeilBrown
2013-07-17 18:24       ` Brassow Jonathan
2013-07-15 15:40 ` Jonathan Brassow [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=1373902849.31715.4.camel@f16 \
    --to=jbrassow@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.