Date: Wed, 09 Nov 2011 00:33:27 +0400 From: "Marat N.Afanasyev" <amarat@ksu.ru> To: Alex Samorukov <ml@os2.kiev.ua> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: smartctl / mpt on 9.0-RC1 Message-ID: <4EB99217.3030508@ksu.ru> In-Reply-To: <4EB7E934.1090703@os2.kiev.ua> References: <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> <20111107114231.GA11028@icarus.home.lan> <4EB7D4D0.9080905@ksu.ru> <20111107130612.GA2298@icarus.home.lan> <4EB7DA61.2030403@os2.kiev.ua> <20111107141004.GA3377@icarus.home.lan> <4EB7E934.1090703@os2.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a cryptographically signed message in MIME format. --------------ms090801080200000204090604 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: quoted-printable Alex Samorukov wrote: > On 11/07/2011 03:10 PM, Jeremy Chadwick wrote: >> I see. I wasn't aware there was an ioctl(2) interface to twa(4). >> >> This makes me wonder: why does Marat use /dev/passX as his device when= >> using smartctl? > Because Marat using LSI mfi (not 3ware twa!) driver in this case. > mfip.ko exports /dev/passX devices for every disk in the raid. >> Could this have some bearing on why he doesn't see the >> necessary data returned from (if even submit to) the underlying disk? >> The syntax of his command was: "smartctl -a /dev/pass1". I would have >> expected the syntax to be "smartctl -a -d 3ware,1 /dev/twa". >> >> What I'm trying to get at here is whether or not smartmontools "does t= he >> right thing" in this situation. Does the output differ between the >> above two syntaxes? I don't see any mention in twa(4)'s man page that >> pass(4) is even registered/used -- though I do see it mentioned that C= AM >> is used by twa(4). > Smartmontools will not work on twa with SAS drives, because it is using= > IOCTL packet format for the ATA protocol. And we need to use SCSI > packets to speak with SAS devices. This code is currently not written. >> >> Furthermore, later comments below indicate CAM isn't involved, which >> further confuses me. Can someone help relieve my confusion on this >> matter? > Because Marat provided output for another controller and another driver= =2E > For me it is also unclear why :) just a little misunderstanding, I suppose ;) I just showed what I'd=20 expect from #smartctl -a -d 3ware,0 /dev/twa0 in case of sas drive on channel 0 --=20 SY, Marat --------------ms090801080200000204090604--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EB99217.3030508>