Ok, I got an update:
After pulling a drive from a RAIDZ2 and leaving the array with no parity overnight I got my daily message. The security run was normal since this wasn't an issue that would reflect on the security log. The daily run had the following:
So now we know. You get a degraded status on the daily run and that's about all.
This output is basically a 'zpool status -v' and nothing more.
After pulling a drive from a RAIDZ2 and leaving the array with no parity overnight I got my daily message. The security run was normal since this wasn't an issue that would reflect on the security log. The daily run had the following:
Code:
Checking status of zfs pools:
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
test 172G 2.28G 170G 1% 1.00x DEGRADED /mnt
pool: test
state: DEGRADED
status: One or more devices could not be opened. Sufficient replicas exist for
the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
see: http://www.sun.com/msg/ZFS-8000-2Q
scan: scrub repaired 0 in 0h0m with 0 errors on Thu Aug 9 01:34:37 2012
config:
NAME STATE READ WRITE CKSUM
test DEGRADED 0 0 0
raidz1-0 DEGRADED 0 0 0
6599038171086723991 UNAVAIL 0 0 0 was /dev/da1p2
da0p2 ONLINE 0 0 0
da1p2 ONLINE 0 0 0
errors: No known data errors
Checking status of ATA raid partitions:
Checking status of gmirror(8) devices:
Checking status of graid3(8) devices:
Checking status of gstripe(8) devices:
So now we know. You get a degraded status on the daily run and that's about all.
This output is basically a 'zpool status -v' and nothing more.