On Fri, October 8, 2010 04:47, Stephan Budach wrote: > So, I decided to give tar a whirl, after zfs send encountered the next > corrupted file, resulting in an I/O error, even though scrub ran > successfully w/o any erors.
I must say that this concept of scrub running w/o error when corrupted files, detectable to zfs send, apparently exist, is very disturbing. Background scrubbing, and the block checksums to make it more meaningful than just reading the disk blocks, was the key thing that drew me into ZFS, and this seems to suggest that it doesn't work. Does your sequence of tests happen to provide evidence that the problem isn't new errors appearing, sometimes after a scrub and before the send? For example, have you done 1) scrub finds no error, 2) send finds error, 3) scrub finds no error? (with nothing in between that could have cleared or fixed the error). -- David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
