On Thursday August 17, [EMAIL PROTECTED] wrote:
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.)
Yes, the message is misleading. I should fix that.
NeilBrown
# echo check
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
In-Reply-To: [EMAIL PROTECTED]
On Mon, 14 Aug 2006 16:14:06 +1000, Neil Brown wrote:
On 2.6.18-rc4 + the below patch:
Drive activity light blinks once on one drive, then the
array status prints (obviously no checking takes place.)
Thanks for the report.
Easily
On Sat, 12 Aug 2006, Chuck Ebbert wrote:
Doing this on a raid1 array:
echo check /sys/block/md0/md/sync_action
On 2.6.16.27:
Activity lights on both mirrors show activity for a while,
then the array status prints on the console.
On 2.6.18-rc4 + the below patch:
Justin Piszcz wrote:
Is there a doc for all of the options you can echo into the sync_action?
I'm assuming mdadm does these as well and echo is just another way to
run work with the array?
How about the obvious, Documentation/md.txt ?
And no, mdadm does not perform or trigger data integrity
Doing this on a raid1 array:
echo check /sys/block/md0/md/sync_action
On 2.6.16.27:
Activity lights on both mirrors show activity for a while,
then the array status prints on the console.
On 2.6.18-rc4 + the below patch:
Drive activity light blinks once on one
