jlo...@ssl.berkeley.edu said: > What's odd is we've checked a few hundred files, and most of them don't > seem to have any corruption. I'm thinking what's wrong is the metadata for > these files is corrupted somehow, yet we can read them just fine. I wish I > could tell which ones are really bad, so we wouldn't have to recreate them > unnecessarily. They are mirrored in various places, or can be recreated > via reprocessing, but recreating/ restoring that many files is no easy task.
You know, this sounds similar to what happened to me once when I did a "zpool offline" to half of a mirror, changed a lot of stuff in the pool (like adding 20GB of data to an 80GB pool), then "zpool online", thinking ZFS might be smart enough to sync up the changes that had happened since detaching. Instead, a bunch of bad files were reported. Since I knew nothing was wrong with the half of the mirror that had never been offlined, I just did a "zpool detach" of the formerly offlined drive, "zpool clear" to clear the error counts, "zpool scrub" to check for integrity, then "zpool attach" to cause resilver to start from scratch. If this describes your situation, I guess the tricky part for you is to now decide which half of your mirror is the good half. There's always "rsync -n -v -a -c ..." to compare copies of files that happen to reside elsewhere. Slow but safe. Regards, Marion _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
