From: raid@bymeinc.com
To: linux-raid@vger.kernel.org
Subject: Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4
Date: Fri, 18 Aug 2006 12:38:58 -0400 (EDT) [thread overview]
Message-ID: <20060818163858.0ABA5AE344@bymeinc.com> (raw)
Neil introduced read-checking into 2.6.16. In versions prior, mirror copies were overwritten instead of checked.
I'm running 2.6.17rc4:
# echo "check" > /sys/block/md0/md/sync_action
# dmesg
md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
md: using 128k window, over a total of 15542784 blocks.
# dstat -d -D sda,sdg
--disk/sda----disk/sdg-
_read write:_read write
81k 30k: 81k 30k
58M 0 : 58M 0
58M 0 : 57M 0
57M 0 : 58M 0
58M 0 : 57M 0
Although the message uses the word "reconscruction," the drives are being checked for consistancy.
-----------------
I just tried the patch and now it seems to be syncing the drives instead
of only checking them? (At the very least the message is misleading.)
# echo "check" >/sys/block/md0/md/sync_action
# dmesg | tail -9
md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
md: using 128k window, over a total of 104256 blocks.
md: md0: sync done.
RAID1 conf printout:
--- wd:2 rd:2
disk 0, wo:0, o:1, dev:hda9
disk 1, wo:0, o:1, dev:sda5
next reply other threads:[~2006-08-18 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 16:38 raid [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-17 20:03 [bug?] raid1 integrity checking is broken on 2.6.18-rc4 Chuck Ebbert
2006-08-28 3:47 ` Neil Brown
2006-08-12 6:49 Chuck Ebbert
2006-08-12 9:13 ` Justin Piszcz
2006-08-12 11:59 ` Michael Tokarev
2006-08-14 6:14 ` Neil Brown
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=20060818163858.0ABA5AE344@bymeinc.com \
--to=raid@bymeinc.com \
--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).