From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 19 14:05:26 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 241A5106564A; Tue, 19 Oct 2010 14:05:26 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id D4C338FC0A; Tue, 19 Oct 2010 14:05:25 +0000 (UTC) Received: by pvg7 with SMTP id 7so303644pvg.13 for ; Tue, 19 Oct 2010 07:05:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SJnUT1mehkASUwjfVD82he0NJvmynqL7NLfgEcjG97w=; b=kNIIWedDgmErJniT9P5YyxW3Q0MTADBUQv3YH3Pk2TMl2RJLUTZQyjKFx7KKvSKzVT u5PYOKb32oMoUYJYMYKzLQ4DKAYnMKbLr5Gy/64ttGO1MOsgtXuWR11qTC84sN8ZhZb0 P7pohX1FQiiTO4eLvogZfIvNGeQM/1F3k3wfE= 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=paiT3qgkqsPHjOdI4OGgyyXlKzR5E5UbrOcffrYxuTVqHlscuefGTOeamw0o/Rzk+X sgclK06mw01jNBGLOwXJ6RTiqWEVYXmXgv5yiVVoaknOsLdUaytel9+xpxi2c7xZbkDK khJyZxUm9z2d7IAcIqk7ihm2IzdJG/eP6r/9I= MIME-Version: 1.0 Received: by 10.229.91.75 with SMTP id l11mr5215807qcm.24.1287497124458; Tue, 19 Oct 2010 07:05:24 -0700 (PDT) Received: by 10.229.61.29 with HTTP; Tue, 19 Oct 2010 07:05:24 -0700 (PDT) In-Reply-To: <201010190849.58660.jhb@freebsd.org> References: <4CB8A614.6000707@greatbaysoftware.com> <201010190849.58660.jhb@freebsd.org> Date: Tue, 19 Oct 2010 18:05:24 +0400 Message-ID: From: Sergey Kandaurov To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Charles Owens , freebsd-current@freebsd.org, Scott Long , freebsd-hardware@freebsd.org Subject: Re: mfiutil reports "PSTATE 0x0020" new drive state X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 14:05:26 -0000 On 19 October 2010 16:49, John Baldwin wrote: > On Monday, October 18, 2010 12:55:18 pm Sergey Kandaurov wrote: >> On 16 October 2010 02:18, Sergey Kandaurov wrote: >> > On 16 October 2010 00:51, Charles Owens = wrote: >> >> =A0Hmm... the problem appears to have resolved itself. =A0After a few= hours the >> >> new drive seems to have gone back into the array, and the original ho= t spare >> >> drive put back into hot-spare state. >> >> >> >> So I'm interpreting state 0x0020 to therefore mean something like "ha= ng on >> >> while I use this new drive to automatically put everything back as it= was >> >> before the failure". =A0Is this correct? >> >> >> >> Thanks, >> >> Charles >> >> >> >> [root@Bsvr ~]# mfiutil show drives >> >> mfi0 Physical Drives: >> >> ( =A0149G) ONLINE =A0SATA enclosu= re 1, slot 0 >> >> ( =A0149G) ONLINE =A0SATA enclosu= re 1, slot 1 >> >> ( =A0149G) ONLINE =A0SATA enclosu= re 1, slot 2 >> >> ( =A0149G) HOT SPARE =A0SATA encl= osure 1, slot >> >> 3 >> >> ( =A0149G) ONLINE =A0SATA enclosu= re 1, slot 4 >> >> >> >> >> >> >>> >> [...] >> >>> [root@svr ~]# mfiutil show drives >> >>> mfi0 Physical Drives: >> >>> ( =A0149G) ONLINE =A0SATA enclos= ure 1, slot >> >>> 0 >> >>> ( =A0149G) ONLINE =A0SATA enclos= ure 1, slot >> >>> 1 >> >>> ( =A0149G) ONLINE =A0SATA enclos= ure 1, slot >> >>> 2 >> >>> ( =A0149G) ONLINE =A0SATA enclos= ure 1, slot >> >>> 3 >> >>> ( =A0149G) PSTATE 0x0020 =A0SATA= enclosure >> >>> 1, slot 4 >> >>> >> >>> mfi0: =A0port 0x1000-0x10ff mem >> >>> ... >> >>> >> > >> > Hi, Charles Owens. >> > >> > 0x20 is much likely to be the copyback physical state, >> > which is missing in enum mfi_pd_state. >> > And what you've experienced is copyback feature in action :) >> > Your array has been rebuilt with HSP as its ordinal PD, then you >> > switched failed drive >> > with good one, and HSP came into copyback mode to move all its data ba= ck >> > to good disk. That prevents reordering of disk numbers in array and >> > double rebuilding. >> > >> >> So, it no one objects, I'd like to commit this change. > > If you have access to the MFI docs (or a reference in the Linux driver, e= .g.) > then this is fine. =A0The existing pd_state enum lists the values for PD = state > that were listed in the MFI docs I had access to at the time I wrote mfiu= til. > Hi, John. I've no such access unfortunately. As for FreeBSD vendor's driver, it doesn't list PD states at all (and looks like their version lags behind other OS versions). However, they (LSI) are listing COPYBACK entry as 0x20 in its Linux driver= , and there: http://lkml.org/lkml/2009/5/5/389 --=20 wbr, pluknet