From owner-freebsd-stable@FreeBSD.ORG Mon Nov 7 14:20:54 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E18D106564A for ; Mon, 7 Nov 2011 14:20:54 +0000 (UTC) (envelope-from ml@os2.kiev.ua) Received: from s1.sdv.com.ua (s1.sdv.com.ua [77.120.97.61]) by mx1.freebsd.org (Postfix) with ESMTP id 2823D8FC18 for ; Mon, 7 Nov 2011 14:20:53 +0000 (UTC) Received: from 80-105-243-80.cust.centrio.cz ([80.243.105.80] helo=[192.168.101.100]) by s1.sdv.com.ua with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RNQ46-000Jsr-2A; Mon, 07 Nov 2011 16:20:51 +0200 Message-ID: <4EB7E934.1090703@os2.kiev.ua> Date: Mon, 07 Nov 2011 15:20:36 +0100 From: Alex Samorukov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Jeremy Chadwick 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> In-Reply-To: <20111107141004.GA3377@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Score: -1.0 Cc: "Marat N.Afanasyev" , FreeBSD Stable Mailing List Subject: Re: smartctl / mpt on 9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2011 14:20:54 -0000 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 the > 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 CAM > 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. For me it is also unclear why :)