[rescue] Solaris ZFS questions

[John Lengeling]

>Can you post the relevant part of "zpool status -xv" ?

So this is what was originally reported

# zpool status
  pool: ccase
 state: DEGRADED
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: resilver completed after 0h45m with 1 errors on Fri Dec  3
07:49:57 2010
config:

        NAME          STATE     READ WRITE CKSUM
        ccase         DEGRADED     2     0     0
          raidz1      DEGRADED     2     0     0
            c0t2d0    ONLINE       6     0     0
            spare     DEGRADED     0     0     0
              c0t3d0  REMOVED      0     0     0
              c0t7d0  ONLINE       0     0     0
            c0t4d0    ONLINE       0     0     0
        spares
          c0t7d0      INUSE     currently in use

errors: No known data errors

I then created a snapshot and started backing up the snapshot and that
is when I came across the read error and here is the new updated zpool
status output that I have now.  My plan was to just back everything up
to a temp drive.  Destroy/create the Pool and restore the data.  I can
handle replacing/restoring the bad file.

# zpool status -xv
  pool: ccase
 state: DEGRADED
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: resilver completed after 0h45m with 1 errors on Fri Dec  3
07:49:57 2010
config:

        NAME          STATE     READ WRITE CKSUM
        ccase         DEGRADED     2     0     0
          raidz1      DEGRADED     2     0     0
            c0t2d0    ONLINE       6     0     0
            spare     DEGRADED     0     0     0
              c0t3d0  REMOVED      0     0     0
              c0t7d0  ONLINE       0     0     0
            c0t4d0    ONLINE       0     0     0
        spares
          c0t7d0      INUSE     currently in use

errors: Permanent errors have been detected in the following files:

        <0x405>:<0x636b6>
        <0x407>:<0x636b6>
        <0x409>:<0x636b6>
        <0x40b>:<0x636b6>
        <0x40d>:<0x636b6>
        <0x40f>:<0x636b6>
        <0x411>:<0x636b6>
        <0x413>:<0x636b6>

/ccase_vobstg/vob7.vbs/s/sdft/9/35/3-867f1db189a811dd9aa90015c5605299-ig

ccase/ccase_vobstg at ccbackup.4:/vob7.vbs/s/sdft/9/35/3-867f1db189a811dd9a
a90015c5605299-ig

ccase/ccase_vobstg at ccbackup.3:/vob7.vbs/s/sdft/9/35/3-867f1db189a811dd9a
a90015c5605299-ig
        <0x3f6>:<0x636b6>

At this point, I have been afraid of doing anything as I don't want to
completely cause a FAILURE on the pool.  Thus what I wanted to be able
to get a good clean backup and then rebuild the pool.

johnl