> From: Stephan Budach [mailto:stephan.bud...@jvm.de] > > > Just in case this wasn't already clear. > > > > After scrub sees read or checksum errors, zpool status -v will list > > filenames that are affected. At least in my experience. > > -- > > - Tuomas > > That didn't do it for me. I used scrub and afterwards zpool staus -v > didn't show any additional corrupted files, although there were the > same three files corrupted in a number of snapshots, which of course > zfs send detected when trying to actually send them.
Budy, we've been over this. The behavior you experienced is explained by having corrupt data inside a hardware raid, and during the scrub you luckily read the good copy of redundant data. During zfs send, you unluckily read the bad copy of redundant data. This is a known problem as long as you use hardware raid. It's one of the big selling points, reasons for ZFS to exist. You should always give ZFS JBOD devices to work on, so ZFS is able to scrub both of the redundant sides of the data, and when a checksum error occurs, ZFS is able to detect *and* correct it. Don't use hardware raid. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
