bash-3.00# zpool status -v nfs-s5-p1
pool: nfs-s5-p1
state: ONLINE
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: http://www.sun.com/msg/ZFS-8000-9P
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
nfs-s5-p1 ONLINE 0 0 2
c4t600C0FF00000000009258F7A4F1BC601d0 ONLINE 0 0 2
errors: No known data errors
bash-3.00#
As you can see there's no protection with ZFS.
Does it mean that those two checksum errors were related to metadata and thanks
to ditto blocks it was corrected? (I assume application did receive proper data
and fs is ok).
btw: I'm really suprised how SATA disks are unreliable. I put dozen TBs of data
on ZFS last time and just after few days I got few hundreds checksum error
(there raid-z was used). And these disks are 500GB in 3511 array. Well that
would explain some fsck's, etc. we saw before.
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
