From owner-freebsd-fs@FreeBSD.ORG Tue Sep 22 19:30:31 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 978C010656A5; Tue, 22 Sep 2009 19:30:31 +0000 (UTC) (envelope-from ktouet@gmail.com) Received: from mail-yw0-f187.google.com (mail-yw0-f187.google.com [209.85.211.187]) by mx1.freebsd.org (Postfix) with ESMTP id 451FD8FC1B; Tue, 22 Sep 2009 19:30:31 +0000 (UTC) Received: by ywh17 with SMTP id 17so67756ywh.3 for ; Tue, 22 Sep 2009 12:30:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=O/TPJq9Tu9laBlTpRr0ogaxBYU6NWZULSwK84bw4dyQ=; b=XY3BYWsNiJ4NU2NqJM/wKGEOkcupUhur0pJhnKoNbuJYgq8nGNkXCphKkIfIAF6luc YKi4ecP/Ee3DbJ3IU8MIO2bqUpgCVW4PfXLVqvKEblHVdDhzLRjnS01UeLtzDtNRspmm Cs5aeGeZ9qO92ulnZryjV9CUTtH3OqnSSao9g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FiGpaGlh2CKOALzbk4znCYs9ks4IclgTMyI+PlwaKFYLyh4QfumpNGrVDn/JDl9Deo OIUShsHOmpxisSa6aq3DyPmt3KMs/FFx2TT9JJrPOho5vWLsghJ+TXIBEIiskZtRDqra bmD+c4cRvIKPg8CQa9VjBmm/YW/AofMIsIhIY= MIME-Version: 1.0 Received: by 10.100.130.11 with SMTP id c11mr1429943and.97.1253647830285; Tue, 22 Sep 2009 12:30:30 -0700 (PDT) In-Reply-To: <20090922125625.GJ6038@garage.freebsd.pl> References: <2a5e326f0909201500w1513aeb5ra644f1c748e22f34@mail.gmail.com> <20090922125625.GJ6038@garage.freebsd.pl> Date: Tue, 22 Sep 2009 13:30:30 -0600 Message-ID: <2a5e326f0909221230m6c7e4828md5f70a5ac6c7892b@mail.gmail.com> From: Kurt Touet To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS - Unable to offline drive in raidz1 based pool X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2009 19:30:31 -0000 On Tue, Sep 22, 2009 at 6:56 AM, Pawel Jakub Dawidek wrot= e: > > Could you send the output of: > > =A0 =A0 =A0 =A0# apply "zdb -l /dev/%1" ad{4,6,12,14} > > -- > Pawel Jakub Dawidek =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://ww= w.wheel.pl > pjd@FreeBSD.org =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http:= //www.FreeBSD.org > FreeBSD committer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Am I Ev= il? Yes, I Am! > I was looking back at the thread, and realized that you had replied to my first message and not the subsequent one (where I had successfully scrubbed and resilvered the drive) -- so the debug output was from the properly resilvered array. Although the one question that still stands (for me), is how the system would have reported itself as healthy after I successfully reattached the failing driving. It strikes me as the type of situation where a checksum error or degraded status should appear. Am I wrong in thinking that, or is there another way in which this could be detected? Looking at James comment, if the one drive had an older txtag, should that have generated a non-healthy state? Cheers, -kurt