Casper.Dik at Sun.COM wrote:
>
> I would suggest that you follow my recipe: not check the boot-archive
> during a reboot. And then report back. (I'm assuming that that will take
> several weeks)
>
May the time has come?
Your recipe has easily prevented me from having to boot to Failsafe just
for an out-of-sync boot archive. Thumbs up!
On the other hand, recently I saw this:
# zpool status
pool: rpool
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: scrub completed after 0h46m with 0 errors on Tue Apr 14 00:19:34
2009
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
c1d0s0 ONLINE 0 0 1
errors: No known data errors
Since it is a rather new drive and has no trouble with Ubuntu, I dared
to clean it:
# zpool clear rpool
and checked it for errors:
# zpool scrub rpool
# zpool status -v
pool: rpool
state: ONLINE
scrub: scrub completed after 0h47m with 0 errors on Tue Apr 14 23:53:48
2009
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
c1d0s0 ONLINE 0 0 0
errors: No known data errors
Now I wonder where that error came from. It couldn't go away with an
earlier scrub, and seemingly left no traces of badness on the drive.
Another inconvenience of ZFS? Or something serious? Maybe introduced
through the recipe?
Curious,
Uwe
