Problem with zpool
jhell
jhell at DataIX.net
Sat Aug 28 02:18:22 UTC 2010
On 08/26/2010 14:08, Adam Stylinski wrote:
> scrub: resilver in progress for 0h9m, 2.16% done, 6h53m to go
You probably want to wait for this to be done before continuing operation.
>
> replacing DEGRADED 0 0 0
> 8991447011275450347 UNAVAIL 0 10.0K 0 was /dev/ad6/old
> ada2 ONLINE 0 0 0 14.1G resilvered
> ada4 ONLINE 0 0 0 56.7M resilvered
>
With the above and the scrub: message these seems just fine.
>
>
> logs DEGRADED 0 0 0
> ada0 ONLINE 0 0 0
Logs in DEGRADED state could be the cause of your whole problem. Add a
spare to that thing and replace the drive if possible or just add
another to it to see if it goes away. PS you wont be able to remove it
but you will be able to offline it if you have enough replicas. Mirror
this vdev as you can not raidzN a log device.
for instance: zpool add topool log mirror ad0 ad1 mirror ad2 ad3
And don't forget!
A raidz group with N disks of size X with P parity disks can hold
approximately (N-P)*X bytes and can withstand P device(s) failing before
data integrity is compromised. The minimum number of devices in a raidz
group is one more than the number of parity disks. The recommended
number is between 3 and 9 to help increase performance.
Regards,
--
jhell,v
More information about the freebsd-fs
mailing list