Date: Tue, 16 Mar 2010 11:07:31 +0200 From: Dan Naumov <dan.naumov@gmail.com> To: Randy Bush <randy@psg.com> Cc: freebsd-fs@freebsd.org Subject: Re: degraded zfs slowdown Message-ID: <cf9b1ee01003160207l1faf4f46kb6ac00ddb39cb782@mail.gmail.com> In-Reply-To: <m21vfkr7ys.wl%randy@psg.com> References: <cf9b1ee01003150409j6f2d23dbr62ede32f0551102a@mail.gmail.com> <m21vfkr7ys.wl%randy@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 16, 2010 at 10:23 AM, Randy Bush <randy@psg.com> wrote: >>> as the ghostly bad drive does not have a unique name, [how] can i tell >>> zfs to remove it for the moment? >> Have you tried running a scrub on the pool and THEN trying to offline >> and detach (zpool commands, not physical actions) the ghost drive? > > =A0 =A0psg.com:/root# zpool scrub tank > =A0 =A0psg.com:/root# zpool status > =A0 =A0 =A0pool: tank > =A0 =A0 state: DEGRADED > =A0 =A0status: One or more devices could not be used because the label is= missing or > =A0 =A0 =A0 =A0 =A0 =A0invalid. =A0Sufficient replicas exist for the pool= to continue > =A0 =A0 =A0 =A0 =A0 =A0functioning in a degraded state. > =A0 =A0action: Replace the device using 'zpool replace'. > =A0 =A0 =A0 see: http://www.sun.com/msg/ZFS-8000-4J > =A0 =A0 scrub: scrub in progress for 0h0m, 0.00% done, 169h12m to go > =A0 =A0config: > > =A0 =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > =A0 =A0 =A0 =A0 =A0 =A0tank =A0 =A0 =A0 =A0DEGRADED =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0mirror =A0 =A0DEGRADED =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0twed1 =A0 FAULTED =A0 =A0 =A00 =A0 =A0 3 = =A0 =A0 0 =A0corrupted data > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0twed1 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 > > =A0 =A0errors: No known data errors > > still do not know how to detach bad drive as it does not have a unique > name As you can see from your own message, the scrub hasn't finished, it has just started. What happens after the scrub is finished? If both twed1's are still visible at this point (after a finished scrub), what happens if you attempt to "zfs detach tank twed1" the ghost drive, do you get an error or does it recognize and correctly remove the ghost twed1? - Sincerely, Dan Naumov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cf9b1ee01003160207l1faf4f46kb6ac00ddb39cb782>