Date: Sun, 10 Aug 2008 17:50:25 +1000 From: Antony Mawer <fbsd-fs@mawer.org> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-fs@freebsd.org, Scott Long <scottl@FreeBSD.org> Subject: Re: zpool degraded - 'UNAVAIL cannot open' functioning drive Message-ID: <489E9DC1.4030802@mawer.org> In-Reply-To: <20080810071117.GA3857@eos.sc1.parodius.com> References: <6c3c36d00808062109y6ae176a0ha055129392b00542@mail.gmail.com> <20080807044759.GA7505@eos.sc1.parodius.com> <6c3c36d00808062212y4e9a1464i48e146e84725a36e@mail.gmail.com> <6c3c36d00808062235v5cbb4470v990b76d569f85614@mail.gmail.com> <20080807055841.GB9735@eos.sc1.parodius.com> <489A9739.20707@yandex.ru> <20080807071434.GA15465@eos.sc1.parodius.com> <489ADD89.8070809@mawer.org> <20080807121245.GA26629@eos.sc1.parodius.com> <489BCA4D.3050704@yandex.ru> <20080810071117.GA3857@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/08/2008 5:11 PM, Jeremy Chadwick wrote: > On Fri, Aug 08, 2008 at 08:23:41AM +0400, Andrey V. Elsukov wrote: >> Jeremy Chadwick wrote: >>> It would be benefitial if there was some form of sysctl to increase the >>> verbosity from the ATA subsystem when an error happens. The existing >>> data we get back is terse, and barely useful. I know for a fact there's >>> more debug information that could be output in such scenarios. And >>> please do not reply with "good idea, send patches" unless you're wanting >>> to be chewed out. :-) >> Ok, I'll try to add some verbose 'printfs' in my branch in perforce :) > > This also starts to enter the realm of why FreeBSD does not implement > support for NCQ -- is this because the ATA driver was built solely > around ATA, rather than AHCI? Linux appears to have two different > drivers depending upon if you're using AHCI or not. FreeBSD's ata(4) > code seems to have everything intermixed/jumbled around, so it looks a > lot like spaghetti... Is this the problem? My understanding of it is that the "legacy" style SATA support is modeled off ATA, while AHCI implements more SCSI-like features (like NCQ). With AHCI mode on Linux, I believe it uses the SCSI subsystem where the infrastructure for things like tagged queuing are available. I thought I heard Scott Long was looking at implementing a SATA subsystem based on CAM at one point, but I gather it succumbed to ENOTIME... --Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?489E9DC1.4030802>