casper....@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)
We are back at square one; or, at the subject line.
I did a zpool status -v, everything was hunky dory.
Next, a power failure, 2 hours later, and this is what zpool status -v
thinks:
zpool status -v
pool: rpool
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
rpool ONLINE 0 0 0
c1d0s0 ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
//etc/svc/repository-boot-20090419_174236
I know, the hord-core defenders of ZFS will repeat for the umpteenth
time that I should be grateful that ZFS can NOTICE and inform about the
problem.
Others might want to repeat that this is not supposed to happen in the
first place.
Reliability at power failure? That was my question, and I had to learn
that the answer is 'no'.
How about my proposal to always have a proper snapshot available? And
after some 4 days without any CKSUM error, how can yanking the power
cord mess boot-stuff?
Uwe
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
