From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 12 03:49:55 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E4A7106564A for ; Mon, 12 Apr 2010 03:49:55 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 34EBF8FC18 for ; Mon, 12 Apr 2010 03:49:55 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1O1AeX-000Amj-PN; Sun, 11 Apr 2010 23:49:37 -0400 Date: Sun, 11 Apr 2010 23:49:37 -0400 From: Gary Palmer To: Brad Waite Message-ID: <20100412034937.GA24680@in-addr.com> References: <4BC280EE.5090202@wcubed.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BC280EE.5090202@wcubed.net> Cc: freebsd-scsi@freebsd.org Subject: Re: QLogic 2360 FC HBAs not playing well with others X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2010 03:49:55 -0000 On Sun, Apr 11, 2010 at 08:09:50PM -0600, Brad Waite wrote: > > > Matthew Jacob wrote: > > >> On 04/09/2010 11:29 AM, Brad Waite wrote: > > >> I beseech you, oh great masters of SCSI and fibre channel, hear my > > pleas > > >> for help! > > >> > > >> My 2 QLE2360s don't appear to be waking up properly in a Dell R710 > > >> running 7.2 AMD64. At the very least, they're not recognizing any of > > >> the volumes on the Sun 2540 array in the fabric. Everything works just > > >> fine under VMware ESXi 4.1, though. > > >> > > > > > > Get newer firmware either by upgrading with RELENG_7 or snagging > > > asm_2300.h from RELENG_7 and rebuilding. > > > > > > You don't have to load all of ispfw > > > > > > isp2300_LOAD=YES > > > > > > should get you just that onemodule > > > > > > the latest in the FreeBSD tree is 3.03.26 > > > > Woot. That helped. Built & installed RELENG_7, but I've got some > > more wierdness. > > Woot. That helped. > > Built & installed RELENG_7, but I've got some more wierdness. > > First off I've got da0 - da15 showing similar to this: > > da0 at isp0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: 200.000MB/s transfers > da0: Command Queueing Enabled > da0: 138989MB (284650656 512 byte sectors: 255H 63S/T 17718C) > > We've got a Sun Storagetek 2540 12-drive array with 4 volumes mapped to > this host. It would appear that it's showing the 4 volumes AND each of > the 12 drives. Is that normal? > > Next, I have about 20 of the following errors for each of da1, da2, da3, > da4, da9, da10, da11 & da12. > > (da1:isp0:0:0:1): READ(6)/WRITE(6) not supported, increasing > minimum_cmd_size to 10. > (da1:isp0:0:0:1): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 > (da1:isp0:0:0:1): CAM Status: SCSI Status Error > (da1:isp0:0:0:1): SCSI Status: Check Condition > (da1:isp0:0:0:1): ILLEGAL REQUEST asc:94,1 > (da1:isp0:0:0:1): Vendor Specific ASC > (da1:isp0:0:0:1): Unretryable error > > What's going on here? > > Is there any config I need to to for volume mapping and/or > multipathing? I'm a complete newb when it comes to FC on FreeBSD, so > forgive my ignorance. > > Thanks for the help, guys! I suspect the reason you have 16 disk devices showing up is that you are running multipath. You will get one da device showing up for each different path, and if you're running a full multipath environment that's likely 4 paths per device, which would lead to the 16 disks (unless they're not the sizes you expect, but I would tend to suspect its a multipath artifact) To handle multipath you probably want to look at gmultipath(8). I'm not sure about READ/WRITE errors. You say they show up for 8 devices? Is it possible that the array is not true active/active on the controllers? Its possible that half the paths are going to a controller that is rejecting the I/O until the LUN fails over, but thats just a guess based on the error message. If you can look at the controller/bus/target/lun information from dmesg and see if you can spot a pattern about the path to the LUNs giving the error that may give a better idea about whats going on. Regards, Gary