Date: Tue, 18 Nov 2014 08:31:43 +0100 From: Borja Marcos <borjam@sarenet.es> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: aacraid drives missing after update 10.0 -> 10.1 ? Message-ID: <A01AEF0E-3D29-4280-9651-6D3D7734FB60@sarenet.es> In-Reply-To: <546A24CD.6040600@multiplay.co.uk> References: <20141116213910.GF44537@home.opsec.eu> <CAHEMsqbKHFatgWuVRbibxpFdmPLnnB76WWMfhcjoQjtk8g8udw@mail.gmail.com> <20141117143323.GH44537@home.opsec.eu> <5133298B-F884-4203-92A0-7D0FCFF72FE1@sarenet.es> <20141117145204.GI44537@home.opsec.eu> <D9A7B574-3C8D-4F6C-A87F-321B92C9A12A@sarenet.es> <546A24CD.6040600@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A01AEF0E-3D29-4280-9651-6D3D7734FB60>