On 07/06/2013 07:55 PM, Christoph Anton Mitterer wrote:

On Fri, 2013-07-05 at 22:19 -0400, Phil Turmel wrote:

quoted

I think you should read Neil's blog entry

I did ;)

quoted

before you get too excited
about raid6check.

Sure it's not a magic wand for all situations... and raid6check itself
seems to be rather at a early starting point...

quoted

You can only trust its decisions when you are
confident that the problems it finds are *only* due to silent read
errors.

Sure.... but at least it can be misused as kinda poor-man's integrity
check.

AFAIU it's not yet working, that it can tell you back through the fs,
which file is affected?

The block layer has no knowledge which file a block belongs to. Even for
file systems that is hard task to figure out, as only inodes store
information which blocks they use. So if you would want to figure out
the corresponding file, you first need to scan through all inodes and
search for the specific block. Once you have the corresponding inode you
need to find directory-entries referencing it. So lots of expensive
reverse searching.



Cheers,
Bernd