Yes. What happened is that you had a transient error which resulted in
EIO being returned to the application. We dutifully recorded this fact
in the persistent error log. When you ran a scrub, it verified that the
blocks were in fact still readable, and hence removed them from the
error log. Me
Eh maybe it's not a problem after all, the scrub has completed well...
--a
bash-3.00# zpool status -v
pool: raidpool
state: ONLINE
scrub: scrub completed with 0 errors on Tue May 9 21:10:55 2006
config:
NAMESTATE READ WRITE CKSUM
raidpoolONLINE 0 0
