Date: Mon, 7 Nov 2011 08:47:23 -0500 From: Andrew Boyer <aboyer@averesystems.com> To: "Marat N.Afanasyev" <amarat@ksu.ru> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>, Alex Samorukov <ml@os2.kiev.ua> Subject: mfip and smartctl Re: smartctl / mpt on 9.0-RC1 Message-ID: <306B653B-4BA6-4946-A493-F77F83AD47CC@averesystems.com> In-Reply-To: <4EB7BFD3.3040606@ksu.ru> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 7, 2011, at 6:24 AM, Marat N.Afanasyev wrote: > > this is an output on mfi controller with mfip loaded: > > # smartctl -a /dev/pass1 > smartctl 5.41 2011-06-09 r3365 [FreeBSD 8.2-RELEASE amd64] (local build) > Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net > > Vendor: SEAGATE > Product: ST3146356SS > Revision: 0007 > User Capacity: 146,815,737,856 bytes [146 GB] > Logical block size: 512 bytes > Logical Unit id: 0x5000c50028f8a56f > Serial number: 3QN4PWHS00009130JLKB > Device type: <31> > Transport protocol: SAS > Local Time is: Mon Nov 7 15:20:27 2011 MSK > Device supports SMART and is Enabled > Temperature Warning Enabled > SMART Health Status: OK > > Current Drive Temperature: 26 C > Drive Trip Temperature: 68 C > > Error counter log: > Errors Corrected by Total Correction Gigabytes Total > ECC rereads/ errors algorithm processed uncorrected > fast | delayed rewrites corrected invocations [10^9 bytes] errors > read: 9382124 0 0 9382124 9382124 3436.782 0 > write: 0 0 0 0 0 8978.360 0 > verify: 663433 0 0 663433 663433 332.651 0 > > Non-medium error count: 7 > > [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. -Andrew > -- > SY, Marat > -------------------------------------------------- Andrew Boyer aboyer@averesystems.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?306B653B-4BA6-4946-A493-F77F83AD47CC>