On Thu, Jan 21, 2016 at 9:27 AM, Lamar Owen lowen@pari.edu wrote:
On 01/20/2016 01:43 PM, Chris Murphy wrote:
On Wed, Jan 20, 2016, 7:17 AM Lamar Owen lowen@pari.edu wrote:
The standard Unix way of refreshing the disk contents is with badblocks' non-destructive read-write test (badblocks -n or as the -cc option to e2fsck, for ext2/3/4 filesystems).
This isn't applicable to RAID, which is what this thread is about. For RAID, use scrub, that's what is for.
The badblocks read/write verification would need to be done on the RAID member devices, not the aggregate md device, for member device level remap. It might need to be done with the md offline, not sure. Scrub? There is a scrub command (and package) in CentOS, but it's meant for secure data erasure, and is not a non-destructive thing. Ah, you're talking about what md will do if 'check' or 'repair' is written to the appropriate location in the sysfs for the md in question. (This info is in the md(4) man page).
Correct.