Date: Mon, 07 Nov 2011 15:06:27 +0100 From: Alex Samorukov <ml@os2.kiev.ua> To: Andrew Boyer <aboyer@averesystems.com> Cc: "Marat N.Afanasyev" <amarat@ksu.ru>, FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: mfip and smartctl Re: smartctl / mpt on 9.0-RC1 Message-ID: <4EB7E5E3.5080109@os2.kiev.ua> In-Reply-To: <306B653B-4BA6-4946-A493-F77F83AD47CC@averesystems.com> References: <4EB1BCAD.7080206@zzattack.org> <20111102233807.GA67112@icarus.home.lan> <4EB1D6F9.3060008@zzattack.org> <20111103000124.GA67550@icarus.home.lan> <4EB1DD51.4080808@zzattack.org> <20111103002352.GA67904@icarus.home.lan> <4EB2538D.3090108@zzattack.org> <4EB2CB75.6070003@os2.kiev.ua> <CAD4099km0FcvUMSw=sY7HB73dtvfQgcVE16VJdGpGK96V%2B4hhA@mail.gmail.com> <4EB2E2D7.2050809@os2.kiev.ua> <CAD4099nogWP5q1GpHyuyWH%2BHUZYmW1xp9BFTdndL7nNLf6vFSw@mail.gmail.com> <4EB2F510.5070804@os2.kiev.ua> <CAD4099nNx7mkyUc2G7Z5W1Y%2B5BOBnP00mfA=F0x17kVoT76Peg@mail.gmail.com> <4EB307CC.8000705@os2.kiev.ua> <4EB6AD22.4080408@ksu.ru> <4EB6B20A.9090104@os2.kiev.ua> <4EB6B530.9000901@ksu.ru> <4EB6F004.9060501@os2.kiev.ua> <4EB6FABF.6060401@os2.kiev.ua> <4EB7BFD3.3040606@ksu.ru> <306B653B-4BA6-4946-A493-F77F83AD47CC@averesystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/07/2011 02:47 PM, Andrew Boyer wrote: > > [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on'] > No self-tests have been logged > Long (extended) Self Test duration: 1740 seconds [29.0 minutes] > > btw, 3dm can tell about reallocated sector count on sas somehow, while smartctl cannot, even on supported controller :( > Notice how the device type is "<31>"? The mfip driver masks off the SCSI INQUIRY peripheral device type bits to prevent CAM from attached da* devices to the disks. See sys/dev/mfi/mfi_cam.c, search for T_DIRECT. That confuses smartctl and prevents it from displaying information like the Grown Defect List. > > I added a local hack to smartctl to interpret a peripheral device type of 0x1f (unknown or missing) to 0x0 (disk), but I don't think the hack is appropriate for general consumption. What we need is better way for mfi and aac to block CAM from attaching without corrupting the inquiry results I can add hack to the sources with checking if underlying driver is mfi (there are already some for buggy SAT fw implementation). It is probably easiest way to do this. I just tested - firmware itself returns correct (disk) status. Of course in the feature its better to fix in mfi_cam to avoid such hacks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EB7E5E3.5080109>