From owner-freebsd-scsi Thu Jun 1 17:52:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id AA86C37B541 for ; Thu, 1 Jun 2000 17:52:10 -0700 (PDT) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id KAA21605; Fri, 2 Jun 2000 10:51:58 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma021592; Fri, 2 Jun 00 10:51:34 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id KAA71297; Fri, 2 Jun 2000 10:51:34 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Fri, 2 Jun 2000 10:51:34 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Matthew Jacob Cc: freebsd-scsi@freebsd.org Subject: Re: QLogic 2200, IBM SAN Data Gateway/Enterprise Storage Server. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Matthew, On Thu, 1 Jun 2000, Matthew Jacob wrote: > just back from vacation....sorry for the delay.. No problems. Ken Merry replied with some info that helped. > Yeah, the deal here is that 2200 card onboard f/w has the SCCLUN code enabled. > But there's no way to tell a priori that it is. Unfortunately, SCCLUN enabling > puts the lun at a different spot in a request queue entry. Ok. I was using a generic kernel that doesn't have the f/w compiled in by default. I rebuilt the kernel with the 2200 f/w compiled in and included Ken's patch and the machine now recognises the drives. It also thinks the first LUN is a disk but gets an error trying to access it. The other two LUNS which really are disks now work fine. I get the following from rawio bash-2.04# ./rawio -a -I ESS-FC -v 1 /dev/da1c Test ID K/sec /sec %User %Sys %Total RR ESS-FC 8396.3 522 0.2 4.3 4.4 16384 SR ESS-FC 21633.9 1320 0.4 9.7 10.1 16384 RW ESS-FC 5498.9 340 0.2 2.6 2.8 16384 SW ESS-FC 18207.9 1111 0.3 8.3 8.6 16384 > I'm very curious as to any issues you might run into with the Shark. Please > let me know how it's going. Well the Shark doesn't natively support FC yet so we're using a "SAN Data Gateway" to map SCSI LUNS to FC LUNS. Native FC support for the Shark is expected soon so I'd expect better performance when it does. Thanks Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message