On Wed, 2015-12-30 at 18:26 +0000, Duncan wrote: > That should work. Cat the files to /dev/null and check dmesg. For > single mode it should check the only copy. For raid1/10 or dup, > running > two checks, ensuring one is even-PID while the other is odd-PID, > should > work to check both copies, since the read-scheduler assigns copy > based on > even/odd PID. Errors will show up in dmesg, as well as cat's STDERR. That doesn't seem very reliable to me, to be honest... plus it wouldn't work in any RAID56 or dupN (with n!=2) case, when that gets sooner or later implemented. Also, I'd kinda guess (or better said: hope) that the kernel's cache would destroy these efforts, at least when the two reads happen mostly in parallel. Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
