Forgot to say, this resilvering is taking ages, second day now:
pool: dati
state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Wed Jul 29 20:25:45 2015
2.77T scanned out of 6.25T at 21.9M/s, 46h23m to go
192G resilvered, 44.26% done
Also, I would expect to have just the taken spare disk to be resilvering, not 
the one that caused the errors.
I suspect the resilvering is taking ages because it's trying to resilver both, 
and the degraded one is slowing it down.
Makes sense?
NAME                          STATE     READ WRITE CKSUM
dati                          DEGRADED     0     0     0
raidz1-0                    DEGRADED     0     0     0
c13t5000CCA0382DB244d0    ONLINE       0     0     0
c13t5000CCA0382DBCCCd0    ONLINE       0     0     0
c13t5000CCA0382DC4ECd0    ONLINE       0     0     0
c13t5000CCA0382DCC38d0    ONLINE       0     0     0
c13t5000CCA0382DD570d0    ONLINE       0     0     0
c13t5000CCA0382DD808d0    ONLINE       0     0     0
spare-6                   DEGRADED     0     0   514
c13t5000CCA0382DDBA0d0  DEGRADED     0     0    19  too many errors  
(resilvering)
c13t5000CCA038322324d0  ONLINE       0     0     0  (resilvering)
raidz1-1                    ONLINE       0     0     0
c13t5000CCA0382F9228d0    ONLINE       0     0     0
Da:
Gabriele Bulfon
A:
[email protected]
Cc:
Aldo Fornoni
Data:
30 luglio 2015 17.28.04 CEST
Oggetto:
[discuss] zpool long resilvering a spare
Hi,
we had a fault to a zpool, and it just got the spare disk and started 
resilvering.
This is the current situation:
NAME                          STATE     READ WRITE CKSUM
dati                          DEGRADED     0     0     0
raidz1-0                    DEGRADED     0     0     0
c13t5000CCA0382DB244d0    ONLINE       0     0     0
c13t5000CCA0382DBCCCd0    ONLINE       0     0     0
c13t5000CCA0382DC4ECd0    ONLINE       0     0     0
c13t5000CCA0382DCC38d0    ONLINE       0     0     0
c13t5000CCA0382DD570d0    ONLINE       0     0     0
c13t5000CCA0382DD808d0    ONLINE       0     0     0
spare-6                   DEGRADED     0     0   514
c13t5000CCA0382DDBA0d0  DEGRADED     0     0    19  too many errors  
(resilvering)
c13t5000CCA038322324d0  ONLINE       0     0     0  (resilvering)
raidz1-1                    ONLINE       0     0     0
c13t5000CCA0382F9228d0    ONLINE       0     0     0
c13t5000CCA0382FC390d0    ONLINE       0     0     0
c13t5000CCA0382FC404d0    ONLINE       0     0     0
c13t5000CCA03825EDC0d0    ONLINE       0     0     0
c13t5000CCA038317E90d0    ONLINE       0     0     0
c13t5000CCA03832240Cd0    ONLINE       0     0     0
c13t5000CCA03832248Cd0    ONLINE       0     0     0
logs
mirror-2                    ONLINE       0     0     0
c13t55CD2E404B474AB7d0s0  ONLINE       0     0     0
c13t55CD2E404B475340d0s0  ONLINE       0     0     0
cache
c13t55CD2E404B474AB7d0s1    ONLINE       0     0     0
c13t55CD2E404B475340d0s1    ONLINE       0     0     0
spares
c13t5000CCA038322324d0      INUSE     currently in use
Questions:
- why are both resilvering the faulted and spare devices?
- why the spare-6 node has 514 cksum and failed ha 19 and spare 0?
- can I safely detach the faulted disk while it's resilvering?
Just to be safe...a suggestion would be nice :)
Gabriele
illumos-discuss
|
Archives
|
Modify
Your Subscription



-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Reply via email to