Sorry for abusing the mailing list, but I don't know how to report bugs anymore and have no visibility of whether this is a known/resolved issue. So, just in case it is not...
With Solaris 11 Express, scrubbing a pool with encrypted datasets for
which no key is currently loaded, unrecoverable read errors are
reported. The error count applies to the pool, and not to any specific
device, which is also somewhat at odds with the "helpful message" text
for diagnostic status and suggested action:
pool: geek
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
scan: scrub repaired 0 in 3h8m with 280 errors on Tue May 10 17:12:15 2011
config:
NAME STATE READ WRITE CKSUM
geek ONLINE 280 0 0
raidz2-0 ONLINE 0 0 0
c13t0d0 ONLINE 0 0 0
c13t1d0 ONLINE 0 0 0
c13t2d0 ONLINE 0 0 0
c13t3d0 ONLINE 0 0 0
c13t4d0 ONLINE 0 0 0
c13t5d0 ONLINE 0 0 0
c0t0d0 ONLINE 0 0 0
c0t1d0 ONLINE 0 0 0
c1t0d0 ONLINE 0 0 0
c1t1d0 ONLINE 0 0 0
Using -v lists an error for the same 2 hexid's in each snapshot, as
per the following example:
geek/crypt@zfs-auto-snap_weekly-2011-03-28-22h39:<0xfffffffffffffffe>
geek/crypt@zfs-auto-snap_weekly-2011-03-28-22h39:<0xffffffffffffffff>
When this has happened previously (on this and other pools) mounting
the dataset by supplying the key, and rerunning the scrub, removes the
errors.
For some reason, I can't in this case (keeps complaining that
the key is wrong). That may be a different issue that has also
happened before, and I will post about separately, once I'm sure I
didn't just made a typo (twice) when first setting the key.
--
Dan.
pgpMX0o7N9c2w.pgp
Description: PGP signature
_______________________________________________ zfs-crypto-discuss mailing list zfs-crypto-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-crypto-discuss
