On Tue, Oct 12, 2010 at 9:39 AM, Stephan Budach <stephan.bud...@jvm.de> wrote: > You are implying that the issues resulted from the H/W raid(s) and I don't > think that this is appropriate. >
Not exactly. Because the raid is managed in hardware, and not by zfs, is the reason why zfs cannot fix these errors when it encounters them. > I configured a striped pool using two raids - this is exactly the same as > using two single hard drives without mirroring them. I simply cannot see what > zfs would be able to do in case of a block corruption in that matter. It cannot, exactly. > You are not stating that a single hard drive is more reliable than a HW raid > box, are you? Actually my pool has no mirror capabilities at all, unless I am > seriously mistaken. no, but zfs-managed raid is more reliable than hardware raid. > What scrub has found out is that none of the blocks had any issue, but the > filesystem was not "clean" either, so if scrub does it's job right and > doesn't report any errors, the error must have occurred somewhere else up the > stack, way before the checksum had been calculated. If the case is, as speculated, that one mirror has bad data and one has good, scrub or any IO has 50% chances of seeing the corruption. scrub does verify checksums. Tuomas _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
