On Feb 18, 2007, at 9:19 PM, Davin Milun wrote:
I have one that looks like this:
pool: preplica-1
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise
restore the
entire pool from backup.
see: http://www.sun.com/msg/ZFS-8000-8A
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
preplica-1 ONLINE 2 0 2
c2t0d0 ONLINE 0 0 0
c2t1d0 ONLINE 0 0 0
c2t2d0 ONLINE 2 0 2
c2t3d0 ONLINE 0 0 0
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
36 3a2939 lvl=0 blkid=0
% uname -a
SunOS preplica01 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Fire-V210
% zpool list
NAME SIZE USED AVAIL CAP HEALTH
ALTROOT
preplica-1 9.06T 8.78T 291G 96% ONLINE -
This is a replicated filesystem, that is kept up to date with zfs
send/recv, and is never even mounted locally. Originally the error
was in a regular inode. So I did the find -inum thing, and found
the filename. I cp'ed the file and deleted the old copy on the
original filesystem, and did some incremental zfs send|recv's to
propagate the fix here. And I expected the problem to go away.
If you run a 'zpool scrub preplica-1', then the persistent error log
will be cleaned up. In the future, we'll have a background scrubber
to make your life easier.
eric
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
