zfs discuss - Oct 2009 - internal scrub keeps restarting resilvering?

After several days of trying to get a 1.5TB drive to resilver and it  
continually restarting, I eliminated all of the snapshot-taking  
facilities which were enabled and

2009-10-29.14:58:41 [internal pool scrub done txg:567780] complete=0
2009-10-29.14:58:41 [internal pool scrub txg:567780] func=1 mintxg=3  
maxtxg=567354
2009-10-29.16:52:53 [internal pool scrub done txg:567999] complete=0
2009-10-29.16:52:53 [internal pool scrub txg:567999] func=1 mintxg=3  
maxtxg=567354
2009-10-29.16:54:09 [internal pool scrub done txg:568003] complete=0
2009-10-29.16:54:09 [internal pool scrub txg:568003] func=1 mintxg=3  
maxtxg=567354
2009-10-29.16:55:24 [internal pool scrub done txg:568007] complete=0
2009-10-29.16:55:24 [internal pool scrub txg:568007] func=1 mintxg=3  
maxtxg=567354

It currently has one drive which is brand new and was just replaced,  
and quite likely another one on the way out:

root at raid3136:~# zpool status raid3149
   pool: raid3149
  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: resilver in progress for 0h10m, 0.05% done, 344h18m to go
config:

         NAME         STATE     READ WRITE CKSUM
         raid3149     ONLINE       0     0     0
           raidz2     ONLINE       0     0     0
             c6t9d0   ONLINE       0     0     0
             c6t10d0  ONLINE       0     0     0
             c6t11d0  ONLINE       0     0     0
             c6t12d0  ONLINE       0     0     0
             c6t13d0  ONLINE       0     0     0
             c6t14d0  ONLINE       0     0     0
             c6t15d0  ONLINE       0     0     0
             c6t16d0  ONLINE       0     0     0
             c6t17d0  ONLINE       0     0     0
             c6t18d0  ONLINE       0     0     0
             c6t19d0  ONLINE       0     0     0
             c6t20d0  ONLINE       0     0     0
             c6t21d0  ONLINE       0     0     0
             c6t22d0  ONLINE       0     0     0  592M resilvered
             c6t23d0  ONLINE       0     0     0
             c6t24d0  ONLINE       0     0     0
             c6t46d0  ONLINE       0     0     0
             c6t47d0  ONLINE       0     0     0
             c6t25d0  ONLINE       0     0     0
             c6t26d0  ONLINE       0     0     0
             c6t48d0  ONLINE       0     0     0
             c6t49d0  ONLINE       0     0     0
             c6t50d0  ONLINE     131     0     0  1.22M resilvered
             c6t51d0  ONLINE       0     0     0

errors: No known data errors


c6t22d0 is the brand new drive and c6t50d0 is the one I think is on  
its way out.

is there any way to disable this internal scrub temporarily so it can  
finish resilvering the pool and I can get that other drive replaced?   
I really don''t want to have to replace both drives at the same time  
since that leaves me with no redundancy in the pool.

-Jeremy

On Oct 29, 2009, at 5:12 PM, Jeremy Kitchen wrote:
> After several days of trying to get a 1.5TB drive to resilver and it  
> continually restarting, I eliminated all of the snapshot-taking  
> facilities which were enabled and
and last night the pool blew that second drive and apparently a third  
and went offline.  After rebooting the machine, everything came up as  
degraded, running a zpool clear got it back going again and it''s  
currently resilvering.  However, it does keep restarting the  
resilvering process, and looking at zpool history -i I''m still seeing  
these internal pool scrubs right about the same time the resilvering  
process starts over.

Is it possible to disable these internal pool scrubs for the time  
being to keep it from restarting the resilvering process?  I''m aware  
that it really only interrupts the process, as any data which has  
already been resilvered is already done, and it''s just leaving where  
it left off, but constantly seeing the resilver status at 1.5%  
complete is rather depressing, and makes it hard for us to give an ETA  
on when it might finish :(

Thanks!

-Jeremy