On 02/16/2011 04:48 PM, NeilBrown wrote: > On Wed, 16 Feb 2011 21:29:39 +0100 Piergiorgio Sartor >> >>> Better reporting of inconsistencies. >>> ------------------------------------ >>> >>> When a 'check' finds a data inconsistency it would be useful if it >>> was reported. That would allow a sysadmin to try to understand the >>> cause and possibly fix it. >> >> Could you, please, consider to add, for RAID-6, the >> capability to report also which device, potentially, >> has the problem? Thanks! > > I would rather leave that to user-space. If I report where the problem is, a > tool could directly read all the blocks in that stripe and perform any fancy > calculations you like. I may even write that tool (but no promises). Hmmm. The existing "check" code, if it encounters a read error, will use available redundancy to recover that data and rewrite it on the spot. Without a read error, or with multiple redundancy, the calculations to check consistency are performed and reported. With all the data "hot", and half the calculation to pinpoint an inconsistency done, it seems a shame to have userspace redo it. Are you adamantly opposed to the kernel doing this? (For Raid6) Code talks, of course, but I'd rather not start if I'm only going to be shot down. Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
