make sense.
The reason of the corruption could be from hardware fault to whatever
buggy application that played with the devices, so unless you can
reproduce I'd ignore this on the kernel side, at least on 2.4 (kernel
trusts metadata, the fs does too, kernel assumes if the data is
corrupted an I/O error has to be generated by the hardware, we can add
some check to make it more robust but it's not a 2.4 matter).
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/