From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 07:31:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3FA4087E for ; Tue, 18 Nov 2014 07:31:50 +0000 (UTC) Received: from cu01176a.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.151]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EDA55C03 for ; Tue, 18 Nov 2014 07:31:48 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPSA id 52FCC9DD3E7; Tue, 18 Nov 2014 08:31:45 +0100 (CET) Subject: Re: aacraid drives missing after update 10.0 -> 10.1 ? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <546A24CD.6040600@multiplay.co.uk> Date: Tue, 18 Nov 2014 08:31:43 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20141116213910.GF44537@home.opsec.eu> <20141117143323.GH44537@home.opsec.eu> <5133298B-F884-4203-92A0-7D0FCFF72FE1@sarenet.es> <20141117145204.GI44537@home.opsec.eu> <546A24CD.6040600@multiplay.co.uk> To: Steven Hartland X-Mailer: Apple Mail (2.1283) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2014 07:31:50 -0000 On Nov 17, 2014, at 5:39 PM, Steven Hartland wrote: > As you say that looks very hack. I'm wondering if the following commit = was the cause: > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D257847 >=20 > Specifically: > = https://svnweb.freebsd.org/base/head/sys/dev/aacraid/aacraid_cam.c?annotat= e=3D257847&pathrev=3D257847#l1231 >=20 > Could you try backing that out and see if it fixes it for you? Now that I notice, my card is not handled by "aacraid", but "aac" = although fortunately the driver structure is pretty similar. In my case, "aac" did never expose the drives, part of a logical volume = or not.=20 Borja.