Date: Fri, 27 Aug 2010 21:46:48 -0400 From: jhell <jhell@DataIX.net> To: Adam Stylinski <kungfujesus06@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: Problem with zpool Message-ID: <4C786A88.20509@DataIX.net> In-Reply-To: <AANLkTimJSw30SSnt%2B49%2BpfqgZxrtoW6yYpgr7WvFo-qB@mail.gmail.com> References: <AANLkTimJSw30SSnt%2B49%2BpfqgZxrtoW6yYpgr7WvFo-qB@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C786A88.20509>