From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Darrick J. Wong" Subject: Re: Multi-Initiator SAS Date: Tue, 19 Sep 2006 13:05:13 -0700 Message-ID: <45104D79.5030001@us.ibm.com> References: <451041AA.4060702@us.ibm.com> <451048C4.2090706@torque.net> Reply-To: "Darrick J. Wong" Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from e34.co.us.ibm.com ([32.97.110.152]:18398 "EHLO e34.co.us.ibm.com") by vger.kernel.org with ESMTP id S1751099AbWISUFQ (ORCPT ); Tue, 19 Sep 2006 16:05:16 -0400 In-Reply-To: <451048C4.2090706@torque.net> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: dougg@torque.net Cc: linux-scsi@vger.kernel.org, Linux Kernel Mailing List Douglas Gilbert wrote: > With the mptsas driver you can use smp_utils to look > at that expander via /dev/mptctl ('modprobe mptctl' first). > To get an overview of what the expander sees, try: > # smp_discover -mb /dev/mptctl Unfortunately, I see this: root@elm3a253:~# smp_discover -mb /dev/mptctl MPTCOMMAND ioctl failed: No such device ioctl failed smp_send_req failed, res=-1 ...a strace of the app reveals this: stat("/dev/mptctl", {st_mode=S_IFCHR|0660, st_rdev=makedev(10, 220), ...}) = 0 open("/dev/mptctl", O_RDWR) = 3 brk(0) = 0x508000 brk(0x529000) = 0x529000 ioctl(3, 0xc0486d14, 0x508010) = -1 ENODEV (No such device) --D