From owner-freebsd-scsi Mon Aug 7 9:44:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from Samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id DD29337BB8A; Mon, 7 Aug 2000 09:44:48 -0700 (PDT) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by Samizdat.uucom.com (8.9.3/8.9.3) id MAA10688; Mon, 7 Aug 2000 12:40:59 -0400 (EDT) To: "Otter" Cc: "Harry Reed" , , Subject: Re: Python 4320 DAT + FreeBSD-4.x References: From: Chris Shenton Date: 07 Aug 2000 12:40:59 -0400 In-Reply-To: "Otter"'s message of "Fri, 4 Aug 2000 14:09:24 -0400" Message-ID: Lines: 45 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 4 Aug 2000 14:09:24 -0400, "Otter" said: Otter> I have an Adaptec 1542CF which worked fine in 2.x and up to Otter> 3.3, at which time I replaced it with a 2940U2W controller and Otter> moved to the 4.0-current branch. I haven't tested it in 4.0 or Otter> 5.0. One of my friends told me he heard that the 154x's don't Otter> work in 4.0 if you have more than 32mb. It sounds like BS to Otter> poor white trash like myself. Is there any truth to this? If Otter> so, what decides the limit? -Otter Works for me in 3.4, 3.5, 4.0, and 4.1. Two SCSI cards, and a Python 4xDDS2 juke (not your model): ahc0: port 0x6c00-0x6cff mem 0xe4101000-0xe4101fff rq 9 at device 8.0 on pci0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0x7400-0x74ff mem 0xe4102000-0xe412fff irq 10 at device 10.0 on pci0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Waiting 5 seconds for SCSI devices to settle ahc0:A:5: refuses synchronous negotiation. Using asynchronous transfers sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) sa1 at ahc0 bus 0 target 5 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 3.300MB/s transfers da0 at ahc0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 8682MB (17781964 512 byte sectors: 255H 63S/T 1106C) da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) ch0 at ahc0 bus 0 target 4 lun 1 ch0: Removable Changer SCSI-2 device ch0: 5.000MB/s transfers (5.000MHz, offset 15) ch0: 4 slots, 1 drive, 1 picker, 0 portals To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 16:44:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from postal.linkfast.net (postal.linkfast.net [208.160.105.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E22A37B5CB for ; Mon, 7 Aug 2000 16:44:07 -0700 (PDT) (envelope-from grasshacker@linkfast.net) Received: by postal.linkfast.net (Postfix, from userid 103) id E5FF39B0D; Mon, 7 Aug 2000 18:44:05 -0500 (CDT) Date: Mon, 7 Aug 2000 18:44:05 -0500 From: GH To: "Kenneth D. Merry" Cc: Darcy Buskermolen , freebsd-scsi@FreeBSD.ORG Subject: Re: AHA29160 Message-ID: <20000807184405.B43832@linkfast.net> References: <3.0.32.20000802153723.020fba50@mail.ok-connect.com> <20000802170527.A38788@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000802170527.A38788@panzer.kdm.org>; from ken@kdm.org on Wed, Aug 02, 2000 at 05:05:27PM -0600 X-OS: FreeBSD Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Aug 02, 2000 at 05:05:27PM -0600, some silly person named Kenneth D. Merry blurbed out > On Wed, Aug 02, 2000 at 15:37:23 -0700, Darcy Buskermolen wrote: > > Has Support for the 64bit Adaptec AHA29160 PCI Scsi Controller found it's > > way into 3.5/4.1/5.0? > > No, yes and yes. > > One note -- in 4.1 and 4.1-stable Adaptec Ultra160 controllers only run at For future reference, there is no 4.1-stable. We have 4.1-RELEASE, and 4-STABLE. G'day, gh > 80MB/sec. They run at 160MB/sec in -current, but the changes haven't been > merged to -stable yet. (They need time to make sure they're stable.) > > Ken > -- > Kenneth Merry > ken@kdm.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 16:54:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id A540837B7BB for ; Mon, 7 Aug 2000 16:54:29 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA79495; Mon, 7 Aug 2000 17:54:24 -0600 (MDT) (envelope-from ken) Date: Mon, 7 Aug 2000 17:54:23 -0600 From: "Kenneth D. Merry" To: GH Cc: Darcy Buskermolen , freebsd-scsi@FreeBSD.ORG Subject: Re: AHA29160 Message-ID: <20000807175423.A79454@panzer.kdm.org> References: <3.0.32.20000802153723.020fba50@mail.ok-connect.com> <20000802170527.A38788@panzer.kdm.org> <20000807184405.B43832@linkfast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000807184405.B43832@linkfast.net>; from grasshacker@linkfast.net on Mon, Aug 07, 2000 at 06:44:05PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Aug 07, 2000 at 18:44:05 -0500, GH wrote: > On Wed, Aug 02, 2000 at 05:05:27PM -0600, some silly person > named Kenneth D. Merry blurbed out > > On Wed, Aug 02, 2000 at 15:37:23 -0700, Darcy Buskermolen wrote: > > > Has Support for the 64bit Adaptec AHA29160 PCI Scsi Controller found it's > > > way into 3.5/4.1/5.0? > > > > No, yes and yes. > > > > One note -- in 4.1 and 4.1-stable Adaptec Ultra160 controllers only run at > > For future reference, there is no 4.1-stable. > We have 4.1-RELEASE, and 4-STABLE. Uhh, yes there is: [ from the RELENG_4 sys/conf/newvers.sh ] ========================================================================== ... # @(#)newvers.sh 8.1 (Berkeley) 4/20/94 # $FreeBSD: src/sys/conf/newvers.sh,v 1.44.2.5 2000/07/26 11:35:21 jkh Exp $ TYPE="FreeBSD" REVISION="4.1" BRANCH="STABLE" RELEASE="${REVISION}-${BRANCH}" SNAPDATE="" if [ "X${SNAPDATE}" != "X" ]; then RELEASE="${RELEASE}-${SNAPDATE}" fi VERSION="${TYPE} ${RELEASE}" ... ========================================================================== And it is an important distinction -- 4.1-stable is -stable *after* 4.1 release but before 4.2-release. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 16:59:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from teapot.egroups.net (teapot.egroups.net [63.204.207.250]) by hub.freebsd.org (Postfix) with SMTP id E0C1137B89F for ; Mon, 7 Aug 2000 16:59:16 -0700 (PDT) (envelope-from kbyanc@egroups.net) Received: (qmail 753 invoked from network); 7 Aug 2000 23:59:15 -0000 Received: (QMFILT: 1.0); 08 Aug 2000 00:59:15 -0000 Received: from unknown (HELO dhcp147.corp.ONElist.com) (192.168.10.147) by teapot with SMTP; 7 Aug 2000 23:59:14 -0000 Date: Mon, 7 Aug 2000 16:59:14 -0700 (PDT) From: Kelly Yancey X-Sender: kbyanc@kbyanc.corp.ONElist.com To: mjacob@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: Using the ses driver 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 We're trying to configure a 4.1-stable box with the ses driver to talk to a Chaparrel RAID. However, after rebuilding the kernel with the ses driver and MAKEDEV'ing a few ses devices, we still get: # pwd /usr/share/examples/ses/getencstat # ./getencstat /dev/ses0 /dev/ses0: Device not configured There is nothing in the dmesg about ses. All we have is: Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (probe0:sym0:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe0:sym0:0:0:0): ILLEGAL REQUEST asc:24,0 (probe0:sym0:0:0:0): Invalid field in CDB (probe0:sym0:0:0:1): Vendor Specific Command. CDB: 1a 20 a 0 14 0 (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:20,0 (probe0:sym0:0:0:1): Invalid command operation code (probe0:sym0:0:0:1): INQUIRY. CDB: 12 21 80 0 ff 0 (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:24,0 (probe0:sym0:0:0:1): Invalid field in CDB Creating DISK da0 pt0 at sym0 bus 0 target 0 lun 1 pt0: Fixed Processor SCSI-2 device pt0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled pt1 at sym0 bus 0 target 5 lun 0 pt1: Fixed Processor SCSI-2 device pt1: Serial Number 1 pt1: 3.300MB/s transfers pass0 at sym0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabl ed pass1 at sym0 bus 0 target 0 lun 1 pass1: Fixed Processor SCSI-2 device pass1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabl ed pass2 at sym0 bus 0 target 5 lun 0 pass2: Fixed Processor SCSI-2 device pass2: Serial Number 1 pass2: 3.300MB/s transfers da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 277227MB (567761920 512 byte sectors: 255H 63S/T 35341C) What are we missing? Thanks, Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 17:16:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7641037B5C0 for ; Mon, 7 Aug 2000 17:16:49 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA17862; Mon, 7 Aug 2000 17:16:49 -0700 Date: Mon, 7 Aug 2000 17:16:51 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kelly Yancey Cc: freebsd-scsi@freebsd.org Subject: Re: Using the ses driver 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 Yuck. Looks like this box doesn't like VPD Inquiries- that'll need a patch in cam_xpt.c. It also doesn't like a Mode Sense either. But neitehr should fatal. Interesting- you've got a JMR JBOD, cool! Mine (fibre channel) nevr seems to want to show up- it's really annoying. I think I actually may have the unit that *doesn't* have the SES module. So- did you add device ses0 and remove device pt0 from your config file? The latter step shouldn't be *required*, but it would clarify some confusion. Because it's showing up as a Processor device, it'll actually be SAF-TE instead of SES, so you'll see something like: ses0 at isp1 bus 0 target 15 lun 0 ses0: Fixed Processor SCSI-2 device ses0: Serial Number 1 ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device The one thing required for SAF-TE to actually be probed out correctly is for the second Inquiry command that comes in and does a longer read of Inquiry data- bytes 44..47 contain info that says that this Processor type device is a SAF-TE compliant device. -matt On Mon, 7 Aug 2000, Kelly Yancey wrote: > > We're trying to configure a 4.1-stable box with the ses driver to talk > to a Chaparrel RAID. However, after rebuilding the kernel with the ses > driver and MAKEDEV'ing a few ses devices, we still get: > # pwd > /usr/share/examples/ses/getencstat > # ./getencstat /dev/ses0 > /dev/ses0: Device not configured > > There is nothing in the dmesg about ses. All we have is: > > Waiting 5 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (probe0:sym0:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe0:sym0:0:0:0): ILLEGAL REQUEST asc:24,0 > (probe0:sym0:0:0:0): Invalid field in CDB > (probe0:sym0:0:0:1): Vendor Specific Command. CDB: 1a 20 a 0 14 0 > (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:20,0 > (probe0:sym0:0:0:1): Invalid command operation code > (probe0:sym0:0:0:1): INQUIRY. CDB: 12 21 80 0 ff 0 > (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:24,0 > (probe0:sym0:0:0:1): Invalid field in CDB > Creating DISK da0 > pt0 at sym0 bus 0 target 0 lun 1 > pt0: Fixed Processor SCSI-2 device > pt0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabled > pt1 at sym0 bus 0 target 5 lun 0 > pt1: Fixed Processor SCSI-2 device > pt1: Serial Number 1 > pt1: 3.300MB/s transfers > pass0 at sym0 bus 0 target 0 lun 0 > pass0: Fixed Direct Access SCSI-2 device > pass0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabl > ed > pass1 at sym0 bus 0 target 0 lun 1 > pass1: Fixed Processor SCSI-2 device > pass1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabl > ed > pass2 at sym0 bus 0 target 5 lun 0 > pass2: Fixed Processor SCSI-2 device > pass2: Serial Number 1 > pass2: 3.300MB/s transfers > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > Enabled > da0: 277227MB (567761920 512 byte sectors: 255H 63S/T 35341C) > > What are we missing? Thanks, > > Kelly > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 17:19:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from postal.linkfast.net (postal.linkfast.net [208.160.105.2]) by hub.freebsd.org (Postfix) with ESMTP id A971A37B89F for ; Mon, 7 Aug 2000 17:19:51 -0700 (PDT) (envelope-from grasshacker@linkfast.net) Received: by postal.linkfast.net (Postfix, from userid 103) id 692EB9B08; Mon, 7 Aug 2000 19:19:51 -0500 (CDT) Date: Mon, 7 Aug 2000 19:19:51 -0500 From: GH To: "Kenneth D. Merry" Cc: Darcy Buskermolen , freebsd-scsi@FreeBSD.ORG Subject: Re: AHA29160 Message-ID: <20000807191951.C43832@linkfast.net> References: <3.0.32.20000802153723.020fba50@mail.ok-connect.com> <20000802170527.A38788@panzer.kdm.org> <20000807184405.B43832@linkfast.net> <20000807175423.A79454@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000807175423.A79454@panzer.kdm.org>; from ken@kdm.org on Mon, Aug 07, 2000 at 05:54:23PM -0600 X-OS: FreeBSD Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Aug 07, 2000 at 05:54:23PM -0600, some silly person named Kenneth D. Merry blurbed out > On Mon, Aug 07, 2000 at 18:44:05 -0500, GH wrote: > > On Wed, Aug 02, 2000 at 05:05:27PM -0600, some silly person > > named Kenneth D. Merry blurbed out > > > On Wed, Aug 02, 2000 at 15:37:23 -0700, Darcy Buskermolen wrote: > > > > Has Support for the 64bit Adaptec AHA29160 PCI Scsi Controller found it's > > > > way into 3.5/4.1/5.0? > > > > > > No, yes and yes. > > > > > > One note -- in 4.1 and 4.1-stable Adaptec Ultra160 controllers only run at > > > > For future reference, there is no 4.1-stable. > > We have 4.1-RELEASE, and 4-STABLE. > > Uhh, yes there is: > > [ from the RELENG_4 sys/conf/newvers.sh ] > ========================================================================== > ... > # @(#)newvers.sh 8.1 (Berkeley) 4/20/94 > # $FreeBSD: src/sys/conf/newvers.sh,v 1.44.2.5 2000/07/26 11:35:21 jkh Exp > $ > > TYPE="FreeBSD" > REVISION="4.1" > BRANCH="STABLE" > RELEASE="${REVISION}-${BRANCH}" > SNAPDATE="" > if [ "X${SNAPDATE}" != "X" ]; then > RELEASE="${RELEASE}-${SNAPDATE}" > fi > VERSION="${TYPE} ${RELEASE}" > ... > ========================================================================== > > And it is an important distinction -- 4.1-stable is -stable *after* 4.1 > release but before 4.2-release. > Good point. Bye now. gh > Ken > -- > Kenneth Merry > ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 17:58:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from teapot.egroups.net (teapot.egroups.net [63.204.207.250]) by hub.freebsd.org (Postfix) with SMTP id 93AAA37B5B1 for ; Mon, 7 Aug 2000 17:58:26 -0700 (PDT) (envelope-from kbyanc@egroups.net) Received: (qmail 7640 invoked from network); 8 Aug 2000 00:58:25 -0000 Received: (QMFILT: 1.0); 08 Aug 2000 01:58:25 -0000 Received: from unknown (HELO dhcp147.corp.ONElist.com) (192.168.10.147) by teapot with SMTP; 8 Aug 2000 00:58:24 -0000 Date: Mon, 7 Aug 2000 17:58:24 -0700 (PDT) From: Kelly Yancey X-Sender: kbyanc@kbyanc.corp.ONElist.com To: Matthew Jacob Cc: freebsd-scsi@freebsd.org Subject: Re: Using the ses driver 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 On Mon, 7 Aug 2000, Matthew Jacob wrote: > > > Yuck. Looks like this box doesn't like VPD Inquiries- that'll need a patch in > cam_xpt.c. It also doesn't like a Mode Sense either. But neitehr should fatal. Would you like a PR? :) > > Interesting- you've got a JMR JBOD, cool! Mine (fibre channel) nevr seems to > want to show up- it's really annoying. I think I actually may have the unit > that *doesn't* have the SES module. > > So- did you add > > device ses0 > > and remove > > device pt0 > > from your config file? The latter step shouldn't be *required*, but it would > clarify some confusion. > > Because it's showing up as a Processor device, it'll actually be SAF-TE > instead of SES, so you'll see something like: > > ses0 at isp1 bus 0 target 15 lun 0 > ses0: Fixed Processor SCSI-2 device > ses0: Serial Number 1 > ses0: 3.300MB/s transfers > ses0: SAF-TE Compliant Device Yep. Worked like a charm when we took out pt0. Apparently this model does have it. :) > > The one thing required for SAF-TE to actually be probed out correctly is for > the second Inquiry command that comes in and does a longer read of Inquiry > data- bytes 44..47 contain info that says that this Processor type device is a > SAF-TE compliant device. > > -matt > Thanks, Kelly > > On Mon, 7 Aug 2000, Kelly Yancey wrote: > > > > > We're trying to configure a 4.1-stable box with the ses driver to talk > > to a Chaparrel RAID. However, after rebuilding the kernel with the ses > > driver and MAKEDEV'ing a few ses devices, we still get: > > # pwd > > /usr/share/examples/ses/getencstat > > # ./getencstat /dev/ses0 > > /dev/ses0: Device not configured > > > > There is nothing in the dmesg about ses. All we have is: > > > > Waiting 5 seconds for SCSI devices to settle > > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > > (probe0:sym0:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 > > (probe0:sym0:0:0:0): ILLEGAL REQUEST asc:24,0 > > (probe0:sym0:0:0:0): Invalid field in CDB > > (probe0:sym0:0:0:1): Vendor Specific Command. CDB: 1a 20 a 0 14 0 > > (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:20,0 > > (probe0:sym0:0:0:1): Invalid command operation code > > (probe0:sym0:0:0:1): INQUIRY. CDB: 12 21 80 0 ff 0 > > (probe0:sym0:0:0:1): ILLEGAL REQUEST asc:24,0 > > (probe0:sym0:0:0:1): Invalid field in CDB > > Creating DISK da0 > > pt0 at sym0 bus 0 target 0 lun 1 > > pt0: Fixed Processor SCSI-2 device > > pt0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > > Enabled > > pt1 at sym0 bus 0 target 5 lun 0 > > pt1: Fixed Processor SCSI-2 device > > pt1: Serial Number 1 > > pt1: 3.300MB/s transfers > > pass0 at sym0 bus 0 target 0 lun 0 > > pass0: Fixed Direct Access SCSI-2 device > > pass0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > > Enabl > > ed > > pass1 at sym0 bus 0 target 0 lun 1 > > pass1: Fixed Processor SCSI-2 device > > pass1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > > Enabl > > ed > > pass2 at sym0 bus 0 target 5 lun 0 > > pass2: Fixed Processor SCSI-2 device > > pass2: Serial Number 1 > > pass2: 3.300MB/s transfers > > da0 at sym0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing > > Enabled > > da0: 277227MB (567761920 512 byte sectors: 255H 63S/T 35341C) > > > > What are we missing? Thanks, > > > > Kelly > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 18: 3: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 978F537B51B for ; Mon, 7 Aug 2000 18:03:00 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA18023; Mon, 7 Aug 2000 18:02:57 -0700 Date: Mon, 7 Aug 2000 18:03:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kelly Yancey Cc: freebsd-scsi@freebsd.org Subject: Re: Using the ses driver 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 > > > > Yuck. Looks like this box doesn't like VPD Inquiries- that'll need a patch in > > cam_xpt.c. It also doesn't like a Mode Sense either. But neitehr should fatal. > > Would you like a PR? :) Sure, but the PR should read: "We're tired of adding goop to cam_xpt.c- need something that the loader can set for cam_xpt to then read" > > > > > Interesting- you've got a JMR JBOD, cool! Mine (fibre channel) nevr seems to > > want to show up- it's really annoying. I think I actually may have the unit > > that *doesn't* have the SES module. > > > > So- did you add > > > > device ses0 > > > > and remove > > > > device pt0 > > > > from your config file? The latter step shouldn't be *required*, but it would > > clarify some confusion. > > > > Because it's showing up as a Processor device, it'll actually be SAF-TE > > instead of SES, so you'll see something like: > > > > ses0 at isp1 bus 0 target 15 lun 0 > > ses0: Fixed Processor SCSI-2 device > > ses0: Serial Number 1 > > ses0: 3.300MB/s transfers > > ses0: SAF-TE Compliant Device > > Yep. Worked like a charm when we took out pt0. Apparently this model > does have it. :) Hmm! That sounds like it warrants a note in ses(4). Send me the dmesg output and a 'getencstat -v' would you for my reference? Thanks! -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 20:16:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dnai.com (dnai.com [207.181.194.98]) by hub.freebsd.org (Postfix) with ESMTP id D920637B506 for ; Mon, 7 Aug 2000 20:16:31 -0700 (PDT) (envelope-from freep@thecity.sfsu.edu) Received: from azoth.dnai.com (azoth.dnai.com [207.181.194.94]) by dnai.com (8.9.3/8.9.3) with ESMTP id UAA38014 for ; Mon, 7 Aug 2000 20:16:31 -0700 (PDT) Received: from mars (dnai-216-15-121-126.cust.dnai.com [216.15.121.126]) by azoth.dnai.com (8.9.3/8.9.3) with SMTP id UAA15340 for ; Mon, 7 Aug 2000 20:16:30 -0700 (PDT) From: "Sam" To: Subject: "tape is now frozen" Date: Mon, 7 Aug 2000 20:17:24 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are using a Tekram DC-315U with Tekram's 3.4 driver with an HP SureStore DAT24i Internal SCSI drive, on a FreeBSD 3.5-STABLE. We can use 'dump' to backup to the drive without errors, but when we try to use 'restore' we get an 'Input/Output' error. We have tried multiple tapes with the same result. Logs follow: [root@sol /]# mt erase 0 [root@sol /]# mt rewind [root@sol /]# mt status Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000 DCLZ ---------available modes--------- 0: 0x24:DDS-2 variable 61000 DCLZ 1: 0x24:DDS-2 variable 61000 DCLZ 2: 0x24:DDS-2 variable 61000 DCLZ 3: 0x24:DDS-2 variable 61000 DCLZ --------------------------------- Current Driver State: at rest. --------------------------------- File Number: 0 Record Number: 0 [root@sol /]# dump 0uaf /dev/nrsa0 /var DUMP: Date of this level 0 dump: Mon Aug 7 19:42:44 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rwd0s1e (/var) to /dev/nrsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 14863 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 14824 tape blocks on 1 volume DUMP: finished in 17 seconds, throughput 872 KBytes/sec DUMP: level 0 dump on Mon Aug 7 19:42:44 2000 DUMP: Closing /dev/nrsa0 DUMP: DUMP IS DONE [root@sol /]# restore -i -s 1 -f /dev/nrsa0 tape read error: Input/output error [root@sol /]# tail /var/log/messages [..removed..] Aug 7 19:45:25 sol /kernel: (sa0:tekram_trm0:0:3:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. [root@sol /]# date Mon 7 Aug 19:46:34 PDT 2000 Any input would be greatly appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 7 23: 2:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E345437BCAC for ; Mon, 7 Aug 2000 23:02:41 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA18779; Mon, 7 Aug 2000 23:02:31 -0700 Date: Mon, 7 Aug 2000 23:02:33 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sam Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: "tape is now frozen" 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 Read the man page and follow what the message says. There was an I/O error that caused the device driver to not know the tape position. There should be some other error reported in the system. On Mon, 7 Aug 2000, Sam wrote: > We are using a Tekram DC-315U with Tekram's 3.4 driver with an HP SureStore > DAT24i Internal SCSI drive, on a FreeBSD 3.5-STABLE. We can use 'dump' to > backup to the drive without errors, but when we try to use 'restore' we get > an 'Input/Output' error. We have tried multiple tapes with the same result. > Logs follow: > > [root@sol /]# mt erase 0 > [root@sol /]# mt rewind > [root@sol /]# mt status > Mode Density Blocksize bpi Compression > Current: 0x24:DDS-2 variable 61000 DCLZ > ---------available modes--------- > 0: 0x24:DDS-2 variable 61000 DCLZ > 1: 0x24:DDS-2 variable 61000 DCLZ > 2: 0x24:DDS-2 variable 61000 DCLZ > 3: 0x24:DDS-2 variable 61000 DCLZ > --------------------------------- > Current Driver State: at rest. > --------------------------------- > File Number: 0 Record Number: 0 > [root@sol /]# dump 0uaf /dev/nrsa0 /var > DUMP: Date of this level 0 dump: Mon Aug 7 19:42:44 2000 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/rwd0s1e (/var) to /dev/nrsa0 > DUMP: mapping (Pass I) [regular files] > DUMP: mapping (Pass II) [directories] > DUMP: estimated 14863 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] > DUMP: DUMP: 14824 tape blocks on 1 volume > DUMP: finished in 17 seconds, throughput 872 KBytes/sec > DUMP: level 0 dump on Mon Aug 7 19:42:44 2000 > DUMP: Closing /dev/nrsa0 > DUMP: DUMP IS DONE > [root@sol /]# restore -i -s 1 -f /dev/nrsa0 > tape read error: Input/output error > [root@sol /]# tail /var/log/messages > [..removed..] > Aug 7 19:45:25 sol /kernel: (sa0:tekram_trm0:0:3:0): tape is now frozen- > use an OFFLINE, REWIND or MTEOM command to clear this state. > [root@sol /]# date > Mon 7 Aug 19:46:34 PDT 2000 > > Any input would be greatly appreciated. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 7:10:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from alchemy.grabstein.net (rx1072.cip.uni-regensburg.de [132.199.216.168]) by hub.freebsd.org (Postfix) with ESMTP id 7456337B7FE for ; Tue, 8 Aug 2000 07:10:35 -0700 (PDT) (envelope-from corex@alchemy.grabstein.net) Received: (from corex@localhost) by alchemy.grabstein.net (8.9.3/8.9.3/GRABSTEIN.NET) id QAA98337; Tue, 8 Aug 2000 16:10:59 +0200 (CEST) (envelope-from corex) Date: Tue, 8 Aug 2000 16:10:59 +0200 From: marius@soylent-green.org To: freebsd-scsi@FreeBSD.ORG Cc: Matthew Jacob Subject: Re: telling CAM to never timeout a transaction Message-ID: <20000808161059.A98325@alchemy.grabstein.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Fix the da driver to have an infinite timeout > hrm, did you already do that or do you have a suggestion or even a patch for it (i didn't see define for it in scsi_da.[ch]) ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 8: 3:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2AC5A37B7C7 for ; Tue, 8 Aug 2000 08:03:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA20220; Tue, 8 Aug 2000 08:03:10 -0700 Date: Tue, 8 Aug 2000 08:03:12 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: marius@soylent-green.org Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: telling CAM to never timeout a transaction In-Reply-To: <20000808161059.A98325@alchemy.grabstein.net> 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 See the call to scsi_read_write in function dastart- it uses DA_DEFAULT_TIMEOUT which is defined at the top of the file. You didn't look very hard. On Tue, 8 Aug 2000 marius@soylent-green.org wrote: > > > > Fix the da driver to have an infinite timeout > > > > hrm, did you already do that or do you have a suggestion or even a patch for it (i didn't see define for it in scsi_da.[ch]) ? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 11:47:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from alchemy.grabstein.net (rx1072.cip.uni-regensburg.de [132.199.216.168]) by hub.freebsd.org (Postfix) with ESMTP id 737AD37B517 for ; Tue, 8 Aug 2000 11:47:49 -0700 (PDT) (envelope-from corex@alchemy.grabstein.net) Received: (from corex@localhost) by alchemy.grabstein.net (8.9.3/8.9.3/GRABSTEIN.NET) id UAA02306; Tue, 8 Aug 2000 20:48:13 +0200 (CEST) (envelope-from corex) Date: Tue, 8 Aug 2000 20:48:13 +0200 From: marius@soylent-green.org To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: telling CAM to never timeout a transaction Message-ID: <20000808204813.A2279@alchemy.grabstein.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > See the call to scsi_read_write in function dastart- it > uses DA_DEFAULT_TIMEOUT which is defined at the top of > the file. You didn't look very hard. > well, i saw it but i'm not into patching kernel sources and was hoping for a comment regarding making the timeout for transactions infinite what would you suggest? setting DA_DEFAULT_TIMEOUT to 0 ? is this save? did you do this already? thanks for your help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 14:49:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from antipater.hosting.swbell.net (antipater.hosting.swbell.net [216.100.99.6]) by hub.freebsd.org (Postfix) with ESMTP id 0AE7B37BFF1 for ; Tue, 8 Aug 2000 14:49:44 -0700 (PDT) (envelope-from alc@imimic.com) Received: from imimic.com (adsl-216-63-78-19.dsl.hstntx.swbell.net [216.63.78.19]) by antipater.hosting.swbell.net id RAA21745; Tue, 8 Aug 2000 17:49:43 -0400 (EDT) [ConcentricHost SMTP Relay 1.7] Message-ID: <39908076.5958A88@imimic.com> Date: Tue, 08 Aug 2000 16:49:42 -0500 From: "Alan L. Cox" Organization: iMimic Networking, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: QL12160A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The hardware release notes for 4.1 say that the Qlogic 12160 controller is supported. Does anyone know if the Qlogic 12160A dual channel controller (note the "A") is also supported? Thanks, Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 14:54: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1BA7D37B675 for ; Tue, 8 Aug 2000 14:54:07 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA21655; Tue, 8 Aug 2000 14:54:06 -0700 Date: Tue, 8 Aug 2000 14:54:06 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Alan L. Cox" Cc: scsi@FreeBSD.ORG Subject: Re: QL12160A In-Reply-To: <39908076.5958A88@imimic.com> 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 Both the 12160 and 12160A are dual channel controllers as far as I know. The 'A' designation is for 66MHZ PCI slots I believe. The answer is "yes". Do not use IBM drives with it (or the 1X80 either). For reasons I have not been able to determine (I'm looking at this, finally, today), writes to IBM drives only are *really* slow. Seagate/Quantum drives seem fine. I thought it might be a f/w negotiation ordering issue, but that's not it so far. On Tue, 8 Aug 2000, Alan L. Cox wrote: > The hardware release notes for 4.1 say that the Qlogic 12160 > controller is supported. Does anyone know if the Qlogic 12160A > dual channel controller (note the "A") is also supported? > > Thanks, > Alan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 16: 1:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from atlas.dnai.com (atlas.dnai.com [207.181.194.95]) by hub.freebsd.org (Postfix) with ESMTP id CBAD837B74B for ; Tue, 8 Aug 2000 16:01:42 -0700 (PDT) (envelope-from freep@thecity.sfsu.edu) Received: from neptune.dnai.com (neptune.dnai.com [207.181.194.93]) by atlas.dnai.com (8.9.3/8.9.3) with ESMTP id QAA05203 for ; Tue, 8 Aug 2000 16:01:42 -0700 (PDT) Received: from mars (dnai-216-15-121-126.cust.dnai.com [216.15.121.126]) by neptune.dnai.com (8.9.3/8.9.3) with SMTP id QAA33674 for ; Tue, 8 Aug 2000 16:01:42 -0700 (PDT) From: "Sam" To: Subject: RE: bad sblock magic number Date: Tue, 8 Aug 2000 16:02:35 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org While trying to "dump" a directory to a tape I get the following results: [root@sol /]# dump -0u -d 97000 -f /dev/nrsa0 /home/files/selling DUMP: Date of this level 0 dump: Tue Aug 8 15:50:11 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /home/files/selling to /dev/nrsa0 DUMP: bad sblock magic number DUMP: The ENTIRE dump is aborted. I was able to dump and restore other directories. Can anyone shed any light on this? What does "bad sblock magic number" mean anyway? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 16:33:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 4AE7C37B85A for ; Tue, 8 Aug 2000 16:33:53 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id JAA19080; Wed, 9 Aug 2000 09:03:36 +0930 (CST) (envelope-from grog) Date: Wed, 9 Aug 2000 09:03:36 +0930 From: Greg Lehey To: Matthew Jacob Cc: Sam , freebsd-scsi@FreeBSD.ORG Subject: Re: "tape is now frozen" Message-ID: <20000809090336.F13974@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from mjacob@feral.com on Mon, Aug 07, 2000 at 11:02:33PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 7 August 2000 at 23:02:33 -0700, Matt Jacob wrote: > On Mon, 7 Aug 2000, Sam wrote: > >> We are using a Tekram DC-315U with Tekram's 3.4 driver with an HP SureStore >> DAT24i Internal SCSI drive, on a FreeBSD 3.5-STABLE. We can use 'dump' to >> backup to the drive without errors, but when we try to use 'restore' we get >> an 'Input/Output' error. We have tried multiple tapes with the same result. >> Logs follow: >> >> [root@sol /]# restore -i -s 1 -f /dev/nrsa0 >> tape read error: Input/output error >> [root@sol /]# tail /var/log/messages >> [..removed..] >> Aug 7 19:45:25 sol /kernel: (sa0:tekram_trm0:0:3:0): tape is now frozen- >> use an OFFLINE, REWIND or MTEOM command to clear this state. >> [root@sol /]# date >> Mon 7 Aug 19:46:34 PDT 2000 >> >> Any input would be greatly appreciated. > > Read the man page and follow what the message says. There was an I/O > error that caused the device driver to not know the tape > position. There should be some other error reported in the system. Indeed, it looks like he omitted the message that we most wanted to see. Let me repeat here that I find this *very* irritating. It happens, for example, if I try to read a block which is too long. There's no way to know the length of a tape block in advance, so this is relatively easy to get, particularly with DDS-4 drives, and it involves a very slow recovery. Why is this needed? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 16:39:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CE42237B868 for ; Tue, 8 Aug 2000 16:39:09 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA22030; Tue, 8 Aug 2000 16:38:59 -0700 Date: Tue, 8 Aug 2000 16:39:03 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Sam , freebsd-scsi@FreeBSD.ORG Subject: Re: "tape is now frozen" In-Reply-To: <20000809090336.F13974@wantadilla.lemis.com> 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 > > Indeed, it looks like he omitted the message that we most wanted to > see. > > Let me repeat here that I find this *very* irritating. It happens, > for example, if I try to read a block which is too long. There's no > way to know the length of a tape block in advance, so this is > relatively easy to get, particularly with DDS-4 drives, and it This error should not occur if you're in variable block mode. If you set the drive in fixed block mode and read a block that's too large, the tape driver cannot know where the tape heads are located. It's that simple. Set your tape drive to variable mode. If the error occurs then, it certainly is wrong and should be fixed. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 16:56: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from atlas.dnai.com (atlas.dnai.com [207.181.194.95]) by hub.freebsd.org (Postfix) with ESMTP id ACC3437B89A for ; Tue, 8 Aug 2000 16:55:58 -0700 (PDT) (envelope-from freep@thecity.sfsu.edu) Received: from azoth.dnai.com (azoth.dnai.com [207.181.194.94]) by atlas.dnai.com (8.9.3/8.9.3) with ESMTP id QAA37717 for ; Tue, 8 Aug 2000 16:55:58 -0700 (PDT) Received: from mars (dnai-216-15-121-126.cust.dnai.com [216.15.121.126]) by azoth.dnai.com (8.9.3/8.9.3) with SMTP id QAA77270 for ; Tue, 8 Aug 2000 16:55:57 -0700 (PDT) From: "Sam" To: Subject: RE: "tape is now frozen" Date: Tue, 8 Aug 2000 16:56:51 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We got it to work by setting the density to the density of the tape: -d 97000 for dds3 -d 61000 for dds2 and dds1 thanks for all your help, Sam -----Original Message----- From: owner-freebsd-scsi@FreeBSD.ORG [mailto:owner-freebsd-scsi@FreeBSD.ORG]On Behalf Of Matthew Jacob Sent: Tuesday, August 08, 2000 4:39 PM To: Greg Lehey Cc: Sam; freebsd-scsi@FreeBSD.ORG Subject: Re: "tape is now frozen" > > Indeed, it looks like he omitted the message that we most wanted to > see. > > Let me repeat here that I find this *very* irritating. It happens, > for example, if I try to read a block which is too long. There's no > way to know the length of a tape block in advance, so this is > relatively easy to get, particularly with DDS-4 drives, and it This error should not occur if you're in variable block mode. If you set the drive in fixed block mode and read a block that's too large, the tape driver cannot know where the tape heads are located. It's that simple. Set your tape drive to variable mode. If the error occurs then, it certainly is wrong and should be fixed. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 8 17: 9: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1F35437B901 for ; Tue, 8 Aug 2000 17:08:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA22168; Tue, 8 Aug 2000 17:08:54 -0700 Date: Tue, 8 Aug 2000 17:08:58 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sam Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: "tape is now frozen" 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 I would appreciate knowing what the actual error messages were in your /var/adm/messages. It's just barely conceivable that reading from known end of recorded media could be *assumed* to not really change tape position, but I'd rather be safe than sorry. Looking at your original email, I see you backed up, using the no-rewind device. Then you tried to restore (without a rewind). Well, yes, the tape driver won't know where you are because you ran past recorded media. The problem here is really then with restore- you were expecting restore to rewind and read from the first file. Cursory examination of the code shows that if the dump number is one, it doesn't do this. Sounds like, woohoo, restore's got another bug. -matt On Tue, 8 Aug 2000, Sam wrote: > We got it to work by setting the density to the density of the tape: > -d 97000 for dds3 > -d 61000 for dds2 and dds1 > > thanks for all your help, > Sam > > -----Original Message----- > From: owner-freebsd-scsi@FreeBSD.ORG > [mailto:owner-freebsd-scsi@FreeBSD.ORG]On Behalf Of Matthew Jacob > Sent: Tuesday, August 08, 2000 4:39 PM > To: Greg Lehey > Cc: Sam; freebsd-scsi@FreeBSD.ORG > Subject: Re: "tape is now frozen" > > > > > > Indeed, it looks like he omitted the message that we most wanted to > > see. > > > > Let me repeat here that I find this *very* irritating. It happens, > > > for example, if I try to read a block which is too long. There's no > > way to know the length of a tape block in advance, so this is > > relatively easy to get, particularly with DDS-4 drives, and it > > This error should not occur if you're in variable block mode. If you set the > drive in fixed block mode and read a block that's too large, the tape driver > cannot know where the tape heads are located. It's that simple. > > Set your tape drive to variable mode. If the error occurs then, it certainly > is wrong and should be fixed. > > > -matt > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 9 18:39:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ipperformance.com (cooper.gilhooley.com [207.8.92.84]) by hub.freebsd.org (Postfix) with ESMTP id 2F46C37B5C7 for ; Wed, 9 Aug 2000 18:39:32 -0700 (PDT) (envelope-from rbg@ipperformance.com) Received: from rbg.gilhooley.com ([10.1.0.66]) by ipperformance.com (8.9.3/8.9.3) with ESMTP id TAA30422 for ; Wed, 9 Aug 2000 19:28:47 -0500 (CDT) (envelope-from rbg@ipperformance.com) Received: from localhost (localhost [127.0.0.1]) by rbg.gilhooley.com (8.9.3/8.9.3) with ESMTP id UAA19233 for ; Wed, 9 Aug 2000 20:36:42 -0500 (CDT) (envelope-from rbg@ipperformance.com) From: rbg@ipperformance.com Date: Wed, 09 Aug 2000 20:36:42 -0500 (CDT) Message-Id: <20000809.203642.38714587.rbg@ipperformance.com> To: freebsd-scsi@freebsd.org Subject: Pass through driver. X-Mailer: Mew version 1.95b43 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, First, I'm a novice with SCSI subsystem so if I ask what appears to be a stupid question, it probably is ;) I created (with the help of the article from daemon news by sergey babkin) a KLD CAM driver and when I load it my driver shows up in the device list (from camcontrol), but does not have a pass-through driver attached to it.. Any hints at what the problem could be ? Thanks, Robert... __________________________________________________________________________ Robert Gordon rbg@ipperformance.com IP Performance, Inc Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 9 19:14: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 63C2937B684 for ; Wed, 9 Aug 2000 19:13:49 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA63087; Wed, 9 Aug 2000 20:13:42 -0600 (MDT) (envelope-from ken) Date: Wed, 9 Aug 2000 20:13:42 -0600 From: "Kenneth D. Merry" To: rbg@ipperformance.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Pass through driver. Message-ID: <20000809201341.A62467@panzer.kdm.org> References: <20000809.203642.38714587.rbg@ipperformance.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000809.203642.38714587.rbg@ipperformance.com>; from rbg@ipperformance.com on Wed, Aug 09, 2000 at 08:36:42PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Aug 09, 2000 at 20:36:42 -0500, rbg@ipperformance.com wrote: > > Hello, > > First, I'm a novice with SCSI subsystem so if I ask what appears > to be a stupid question, it probably is ;) > > I created (with the help of the article from daemon news by > sergey babkin) a KLD CAM driver and when I load it my driver shows > up in the device list (from camcontrol), but does not have a > pass-through driver attached to it.. Any hints at what the problem > could be ? Well, what sort of driver is this? A peripheral driver, a HBA/SIM driver, or what? In any case, the pass(4) device only attaches to SCSI targets, so it can't attach to another peripheral driver or a HBA driver. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 10 2:49:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id CCD4837B980; Thu, 10 Aug 2000 02:49:50 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 13MoyB-000GYI-0A; Thu, 10 Aug 2000 09:49:48 +0000 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id SAA77459; Wed, 9 Aug 2000 18:14:28 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id SAA05231; Wed, 9 Aug 2000 18:04:27 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Wed, 9 Aug 2000 18:04:26 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: freebsd-scsi@FreeBSD.org Cc: gibbs@FreeBSD.org Subject: CAM - The Module - Call for testers Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-176558756-965840666=:5091" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-176558756-965840666=:5091 Content-Type: TEXT/PLAIN; charset=US-ASCII The USB Mass Storage driver uses CAM. At the moment CAM needs to be compiled into the kernel for the umass driver to work. The following patch makes CAM a module. As far as I can test it loads and runs fine, but that is only with a limited testcase, one USB floppy drive. I'd appreciate it if someone with at least a SCSI adapter and at least one SCSI device attached to it, could do the following: - compile a kernel without scbus, da, cd, sa and other SCSI devices - recompile the umass module after the patch has been applied - compile the cam module - add umass_load to your /boot/loader.conf (which will pull in cam.ko through a dependency) This should work even in the case of a SCSI adapter plus drive from which you boot. Or at least that's the idea :-} Thanks in advance! Nick -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ --0-176558756-965840666=:5091 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="cam.module.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="cam.module.diff" SW5kZXg6IGRldi91c2IvdW1hc3MuYw0KPT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PQ0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3N5cy9kZXYvdXNiL3VtYXNz LmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjI5DQpkaWZmIC13IC11IC1y MS4yOSB1bWFzcy5jDQotLS0gZGV2L3VzYi91bWFzcy5jCTIwMDAvMDcvMzAg MTc6NTQ6MzQJMS4yOQ0KKysrIGRldi91c2IvdW1hc3MuYwkyMDAwLzA4LzA4 IDE5OjMzOjM1DQpAQCAtNTM0LDYgKzUzNCw5IEBADQogCQkJCWludCBidWZs ZW4sIGludCBwcmludGxlbik7DQogI2VuZGlmDQogDQorI2lmIGRlZmluZWQo X19GcmVlQlNEX18pDQorTU9EVUxFX0RFUEVORCh1bWFzcywgY2FtLCAxLDEs MSk7DQorI2VuZGlmDQogDQogLyoNCiAgKiBVU0IgZGV2aWNlIHByb2JlL2F0 dGFjaC9kZXRhY2gNCkluZGV4OiBjYW0vY2FtX3hwdC5jDQo9PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09DQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL2Nh bS9jYW1feHB0LmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjkwDQpkaWZm IC13IC11IC1yMS45MCBjYW1feHB0LmMNCi0tLSBjYW0vY2FtX3hwdC5jCTIw MDAvMDgvMDggMDY6NDk6MzMJMS45MA0KKysrIGNhbS9jYW1feHB0LmMJMjAw MC8wOC8wOSAxNjo0MTozMQ0KQEAgLTYyOSw5ICs2MjksMjAgQEANCiAjZW5k aWYgLyogQ0FNX0RFQlVHX0JVUyB8fCBDQU1fREVCVUdfVEFSR0VUIHx8IENB TV9ERUJVR19MVU4gKi8NCiANCiAvKiBPdXIgYm9vdC10aW1lIGluaXRpYWxp emF0aW9uIGhvb2sgKi8NCitzdGF0aWMgaW50IGNhbV9tb2R1bGVfZXZlbnRf aGFuZGxlcihtb2R1bGVfdCwgaW50IC8qbW9kZXZlbnR0eXBlX3QqLywgdm9p ZCAqKTsNCisNCitzdGF0aWMgbW9kdWxlZGF0YV90IGNhbV9tb2R1bGVkYXRh ID0gew0KKwkiY2FtIiwNCisJY2FtX21vZHVsZV9ldmVudF9oYW5kbGVyLA0K KwlOVUxMDQorfTsNCisNCiBzdGF0aWMgdm9pZAl4cHRfaW5pdCh2b2lkICop Ow0KLVNZU0lOSVQoY2FtLCBTSV9TVUJfQ09ORklHVVJFLCBTSV9PUkRFUl9T RUNPTkQsIHhwdF9pbml0LCBOVUxMKTsNCiANCitERUNMQVJFX01PRFVMRShj YW0sIGNhbV9tb2R1bGVkYXRhLCBTSV9TVUJfQ09ORklHVVJFLCBTSV9PUkRF Ul9TRUNPTkQpOw0KK01PRFVMRV9WRVJTSU9OKGNhbSwgMSk7DQorDQorDQog c3RhdGljIGNhbV9zdGF0dXMJeHB0X2NvbXBpbGVfcGF0aChzdHJ1Y3QgY2Ft X3BhdGggKm5ld19wYXRoLA0KIAkJCQkJIHN0cnVjdCBjYW1fcGVyaXBoICpw ZXJwaCwNCiAJCQkJCSBwYXRoX2lkX3QgcGF0aF9pZCwNCkBAIC0xMjY0LDYg KzEyNzUsMTggQEANCiAJfQ0KIA0KIAlyZXR1cm4oZXJyb3IpOw0KK30NCisN CitzdGF0aWMgaW50DQorY2FtX21vZHVsZV9ldmVudF9oYW5kbGVyKG1vZHVs ZV90IG1vZCwgaW50IHdoYXQsIHZvaWQgKmFyZykNCit7DQorCWlmICh3aGF0 ID09IE1PRF9MT0FEKSB7DQorCQl4cHRfaW5pdChOVUxMKTsNCisJfSBlbHNl IGlmICh3aGF0ID09IE1PRF9VTkxPQUQpIHsNCisJCXJldHVybiBFQlVTWTsN CisJfQ0KKw0KKwlyZXR1cm4gMDsNCiB9DQogDQogLyogRnVuY3Rpb25zIGFj Y2Vzc2VkIGJ5IHRoZSBwZXJpcGhlcmFsIGRyaXZlcnMgKi8NCg== --0-176558756-965840666=:5091 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="cam.module.Makefile" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="cam.module.Makefile" IyAgICAgICAkRnJlZUJTRCQgDQoNCk1BSU5UQUlORVIJID0gbl9oaWJtYUBm cmVlYnNkLm9yZw0KUwkJID0gJHsuQ1VSRElSfS8uLi8uLg0KDQouUEFUSDoJ CSAkUy9jYW0gJFMvY2FtL3Njc2kNCktNT0QJCSA9IGNhbQ0KDQojIFNlZSBz eXMvY29uZi9vcHRpb25zIGZvciB0aGUgZmxhZ3MgdGhhdCBnbyBpbnRvIHRo ZSBkaWZmZXJlbnQgb3B0XyouaCBmaWxlcy4NClNSQ1MJCSA9IG9wdF9jYW0u aA0KU1JDUwkJKz0gb3B0X3Njc2kuaA0KU1JDUwkJKz0gb3B0X2NkLmgNClNS Q1MJCSs9IG9wdF9od193ZG9nLmgNClNSQ1MJCSs9IG9wdF9wdC5oDQpTUkNT CQkrPSBvcHRfc2EuaA0KU1JDUwkJKz0gb3B0X3Nlcy5oDQpTUkNTCQkrPSBk ZXZpY2VfaWYuaCBidXNfaWYuaA0KU1JDUwkJKz0gY2FtLmMgY2FtX2V4dGVu ZC5jIGNhbV9wZXJpcGguYyBjYW1fcXVldWUuYw0KU1JDUwkJKz0gY2FtX3Np bS5jIGNhbV94cHQuYw0KU1JDUwkJKz0gc2NzaV9hbGwuYyBzY3NpX2NkLmMg c2NzaV9jaC5jDQpTUkNTCQkrPSBzY3NpX2RhLmMNClNSQ1MJCSs9IHNjc2lf cGFzcy5jDQpTUkNTCQkrPSBzY3NpX3B0LmMNClNSQ1MJCSs9IHNjc2lfc2Eu Yw0KU1JDUwkJKz0gc2NzaV9zZXMuYw0KU1JDUwkJKz0gc2NzaV90YXJnX2Jo LmMgc2NzaV90YXJnZXQuYw0KDQpOT01BTgkJID0NCg0Kb3B0X3Njc2kuaDoN CgkJZWNobyAnI2RlZmluZSBTQ1NJX0RFTEFZIDE1MDAwJyA+IG9wdF9zY3Np LmgNCg0KLmluY2x1ZGUgPGJzZC5rbW9kLm1rPg0K --0-176558756-965840666=:5091-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 10 12:22:13 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from northlink.com (northlink.com [216.19.0.216]) by hub.freebsd.org (Postfix) with ESMTP id F333637BC1B for ; Thu, 10 Aug 2000 12:22:06 -0700 (PDT) (envelope-from jmodjeski@ms1.northlink.com) Received: from ms1.northlink.com (ms1.northlink.com [216.19.4.28]) by northlink.com (8.9.1/8.9.1) with ESMTP id MAA21152 for ; Thu, 10 Aug 2000 12:21:18 -0700 (MST) X-Real-From: jmodjeski@ms1.northlink.com X-Real-To: Received: by MS1 with Internet Mail Service (5.5.2650.21) id ; Thu, 10 Aug 2000 12:09:50 -0700 Message-ID: <00101B7A7FDDD311A89500A0CC56C79048B0@MS1> From: Joe Modjeski To: "'freebsd-scsi@freebsd.org'" Subject: to Vinum or not to Vinum Date: Thu, 10 Aug 2000 12:09:47 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Currently we have 3 Compaq Proliant 1600R servers with 6 9.1 Ultra3 drives in each. We are attempting (very unsuccessfully) to do Raid5 with vinum. We get fatal trap 12 errors very regularly and after a few reboots the vinum volume is so chewed up that we end up having to rebuild the system. I tracked down the majority of the problems to the /etc/security script. I believe it is about the 6th or 7th line down where it starts the find run. The box starts off fine but after about 1 minute it starts to hit all the drives at once then BLAM!! It gives me the error. The error can also happen eratically for no apparent reason. Like while uploading a file via ftp. Maybe a 1 or 2 Meg file. Then there are times when it should happen but it doesn't like making MySQL with gmake -j90. The SCSI adaper that comes with the machine is Symbios 835c876. The hotswap controller is also a Symbios ( I forgot the number ). We have tried swapping in an adaptec 2940UW but the error actually gets worse. The other option that has come up is to install a DPT SmartRaid IV card. The after I suggested it the bossman found a few people that mailed list quite a few months ago having problems with the card, Aug '99. Have these problems been worked out? Does anybody have some success/failure stories to share with me so I have some ammo one way or another. These boxes are about a month late for deadline, and the boss is starting to think Linux will be the big solution (Makes stomach turn). They are replacement Authentication and Webservers, so stability is a MAJOR concern. I would like to avoid the 2AM calls. Thanks in advance for any help/suggestions. Joe Modjeski Administrator jmodjeski@northlink.com Northlink LLC 450 W Goodwin Suite 107 Phone: (520) 445-0707 Fax: (520) 541-0096 http://www.northlink.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 10 18:59:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 5A72837BB68 for ; Thu, 10 Aug 2000 18:59:16 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.9.3/8.9.3) with ESMTP id SAA91916 for ; Thu, 10 Aug 2000 18:59:11 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <39935DF5.9FBDB44F@vpop.net> Date: Thu, 10 Aug 2000 18:59:17 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Porting an app from old SCSI system to CAM Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to get DATlib (ftp://ftp.informatik.uni-erlangen.de/pub/DATlib/) running on FreeBSD 4.1-STABLE. From what I can tell, all I need to do is to reimplement one subroutine (see below). How do I do this? Matt #ifdef __FreeBSD__ /* doesn't look like generic BSD */ #include int send_scsi_command( int scsifd, unsigned char *cmd,int cmdlen, unsigned char *inbuf,int inbuflen, unsigned char *outbuf,int outbuflen, unsigned char *rqbuf,int rqbuflen ) { scsireq_t ucmd; int r; memset (&ucmd, '\0', sizeof (ucmd)); ucmd.flags = 0; ucmd.timeout = 1000; memcpy (ucmd.cmd, (caddr_t)cmd, cmdlen); ucmd.cmdlen = cmdlen; if (inbuf) { ucmd.flags |= SCCMD_READ; ucmd.databuf =(caddr_t)inbuf; ucmd.datalen = inbuflen; } else { ucmd.flags |= SCCMD_WRITE; ucmd.databuf = (caddr_t)outbuf; ucmd.datalen = outbuflen; } if (rqbuf) ucmd.flags|=0; /* FIXME: Huh? Arne? */ r = ioctl(scsifd,SCIOCCOMMAND,&ucmd); if (rqbuf) memcpy (rqbuf, ucmd.sense, rqbuflen); return r; } /* send_scsi_command */ #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 10 19:35:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7ECE537BBBA for ; Thu, 10 Aug 2000 19:35:55 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id MAA07695; Fri, 11 Aug 2000 12:05:41 +0930 (CST) (envelope-from grog) Date: Fri, 11 Aug 2000 12:05:41 +0930 From: Greg Lehey To: Joe Modjeski Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: to Vinum or not to Vinum Message-ID: <20000811120541.G66881@wantadilla.lemis.com> References: <00101B7A7FDDD311A89500A0CC56C79048B0@MS1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <00101B7A7FDDD311A89500A0CC56C79048B0@MS1>; from jmodjeski@ms1.northlink.com on Thu, Aug 10, 2000 at 12:09:47PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 10 August 2000 at 12:09:47 -0700, Joe Modjeski wrote: > Currently we have 3 Compaq Proliant 1600R servers with 6 9.1 Ultra3 drives > in each. We are attempting (very unsuccessfully) to do Raid5 with vinum. > We get fatal trap 12 errors very regularly and after a few reboots the vinum > volume is so chewed up that we end up having to rebuild the system. I > tracked down the majority of the problems to the /etc/security script. I > believe it is about the 6th or 7th line down where it starts the find run. > The box starts off fine but after about 1 minute it starts to hit all the > drives at once then BLAM!! It gives me the error. It would be nice to know some details. A dump, for example, or what version of Vinum you're running. You might like to take a look at http://www.lemis.com/vinum/how-to-debug.html. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 11 15:23:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 02BB337B5A3 for ; Fri, 11 Aug 2000 15:23:30 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00752; Fri, 11 Aug 2000 15:34:53 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008112234.PAA00752@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Reimer Cc: freebsd-scsi@freebsd.org Subject: Re: Porting an app from old SCSI system to CAM In-reply-to: Your message of "Thu, 10 Aug 2000 18:59:17 PDT." <39935DF5.9FBDB44F@vpop.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Aug 2000 15:34:53 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm trying to get DATlib > (ftp://ftp.informatik.uni-erlangen.de/pub/DATlib/) running on FreeBSD > 4.1-STABLE. From what I can tell, all I need to do is to reimplement one > subroutine (see below). > > How do I do this? Have a look at the cdrecord port, which has similar requirements. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 11 17:53: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from northlink.com (northlink.com [216.19.0.216]) by hub.freebsd.org (Postfix) with ESMTP id 21CEB37BC4A for ; Fri, 11 Aug 2000 17:52:58 -0700 (PDT) (envelope-from jmodjeski@ms1.northlink.com) Received: from ms1.northlink.com (ms1.northlink.com [216.19.4.28]) by northlink.com (8.9.1/8.9.1) with ESMTP id RAA21482; Fri, 11 Aug 2000 17:52:48 -0700 (MST) X-Real-From: jmodjeski@ms1.northlink.com X-Real-To: freebsd-scsi@freebsd.org Received: by MS1 with Internet Mail Service (5.5.2650.21) id ; Fri, 11 Aug 2000 17:40:26 -0700 Message-ID: <00101B7A7FDDD311A89500A0CC56C79048B8@MS1> From: Joe Modjeski To: "'Greg Lehey'" Cc: "'freebsd-scsi@freebsd.org'" Subject: RE: to Vinum or not to Vinum Date: Fri, 11 Aug 2000 17:40:26 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FreeBSD 4.0-RELEASE #0 The default vinum version that came with 4.0. no source changes. I use a minimal install and then map the /usr /var /tmp directories to the Vinum drive once setup. Then extract the kernel source and install ports to the Raid5 volume vinum list: 5 drives: D Raid51 State: up Device /dev/da1s1e Avail: 0/8675 MB (0%) D Raid52 State: up Device /dev/da2s1e Avail: 0/8675 MB (0%) D Raid53 State: up Device /dev/da3s1e Avail: 0/8675 MB (0%) D Raid54 State: up Device /dev/da4s1e Avail: 0/8675 MB (0%) D Raid55 State: up Device /dev/da5s1e Avail: 0/8675 MB (0%) 1 volumes: V Raid5 State: up Plexes: 1 Size: 33 GB 1 plexes: P Raid5.p0 R5 State: up Subdisks: 5 Size: 33 GB 5 subdisks: S Raid5.p0.s0 State: up PO: 0 B Size: 8675 MB S Raid5.p0.s1 State: up PO: 512 kB Size: 8675 MB S Raid5.p0.s2 State: up PO: 1024 kB Size: 8675 MB S Raid5.p0.s3 State: up PO: 1536 kB Size: 8675 MB S Raid5.p0.s4 State: up PO: 2048 kB Size: 8675 MB I am working on getting the dumps but it is not as easy as it sounds in the handbook or the link. I would like to try the version of vinum that was stated to be patched on the vinum page: 28 September 1999: We have seen hangs when perform heavy I/O to RAID-5 plexes. The symptoms are that processes hang waiting on vrlock and flswai. Use ps lax to display this information. Technical explanation: A deadlock arose between code locking stripes on a RAID-5 plex (vrlock) and code waiting for buffers to be freed (flswai). Status: Fix committed to FreeBSD-CURRENT on 5 January 2000. We're waiting to be reasonably sure that the problem doesn't reoccur, then it will be committed to -STABLE. Actually after looking at the bug report again. I am sure find locks in a state (vrlock) - using ps axl - noticed this while trying to create the crash dump today. I will have to pick this up on Monday. Have a good weekend all. Joe jmodjeski@northlink.com -----Original Message----- From: Greg Lehey [mailto:grog@lemis.com] Sent: Thursday, August 10, 2000 7:36 PM To: Joe Modjeski Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: to Vinum or not to Vinum On Thursday, 10 August 2000 at 12:09:47 -0700, Joe Modjeski wrote: > Currently we have 3 Compaq Proliant 1600R servers with 6 9.1 Ultra3 drives > in each. We are attempting (very unsuccessfully) to do Raid5 with vinum. > We get fatal trap 12 errors very regularly and after a few reboots the vinum > volume is so chewed up that we end up having to rebuild the system. I > tracked down the majority of the problems to the /etc/security script. I > believe it is about the 6th or 7th line down where it starts the find run. > The box starts off fine but after about 1 minute it starts to hit all the > drives at once then BLAM!! It gives me the error. It would be nice to know some details. A dump, for example, or what version of Vinum you're running. You might like to take a look at http://www.lemis.com/vinum/how-to-debug.html. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 11 18:22:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 2AE5137BCA4 for ; Fri, 11 Aug 2000 18:22:05 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id KAA19714; Sat, 12 Aug 2000 10:51:57 +0930 (CST) (envelope-from grog) Date: Sat, 12 Aug 2000 10:51:57 +0930 From: Greg Lehey To: Joe Modjeski Cc: freebsd-scsi@freebsd.org Subject: Re: to Vinum or not to Vinum Message-ID: <20000812105156.E69211@wantadilla.lemis.com> References: <00101B7A7FDDD311A89500A0CC56C79048B8@MS1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <00101B7A7FDDD311A89500A0CC56C79048B8@MS1>; from jmodjeski@ms1.northlink.com on Fri, Aug 11, 2000 at 05:40:26PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 11 August 2000 at 17:40:26 -0700, Joe Modjeski wrote: > > FreeBSD 4.0-RELEASE #0 > > The default vinum version that came with 4.0. > > no source changes. I use a minimal install and then map the /usr /var /tmp > directories to the Vinum drive once setup. Then extract the kernel source > and install ports to the Raid5 volume > > vinum list: > 5 drives: > D Raid51 State: up Device /dev/da1s1e Avail: > 0/8675 MB (0%) Please don't wrap these lines. > D Raid52 State: up Device /dev/da2s1e Avail: > 0/8675 MB (0%) > D Raid53 State: up Device /dev/da3s1e Avail: > 0/8675 MB (0%) > D Raid54 State: up Device /dev/da4s1e Avail: > 0/8675 MB (0%) > D Raid55 State: up Device /dev/da5s1e Avail: > 0/8675 MB (0%) > > 1 volumes: > V Raid5 State: up Plexes: 1 Size: 33 GB > > 1 plexes: > P Raid5.p0 R5 State: up Subdisks: 5 Size: 33 GB > > 5 subdisks: > S Raid5.p0.s0 State: up PO: 0 B Size: 8675 MB > S Raid5.p0.s1 State: up PO: 512 kB Size: 8675 MB > S Raid5.p0.s2 State: up PO: 1024 kB Size: 8675 MB > S Raid5.p0.s3 State: up PO: 1536 kB Size: 8675 MB > S Raid5.p0.s4 State: up PO: 2048 kB Size: 8675 MB > > I am working on getting the dumps but it is not as easy as it sounds in the > handbook or the link. Don't bother, upgrade to 4-STABLE or 4.1-RELEASE. > I would like to try the version of vinum that was stated to be patched on > the vinum page: > > 28 September 1999: We have seen hangs when perform heavy I/O to RAID-5 > plexes. The symptoms are that processes hang waiting on vrlock and flswai. > Use ps lax to display this information. > Technical explanation: A deadlock arose between code locking stripes on a > RAID-5 plex (vrlock) and code waiting for buffers to be freed (flswai). > > Status: Fix committed to FreeBSD-CURRENT on 5 January 2000. We're waiting to > be reasonably sure that the problem doesn't reoccur, then it will be > committed to -STABLE. > > Actually after looking at the bug report again. I am sure find locks in a > state (vrlock) - using ps axl - noticed this while trying to create the > crash dump today. Hmm. Yes, it's possible that remnants of this bug were still in 4.0. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 12 0:23:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 8929837B6AB for ; Sat, 12 Aug 2000 00:23:40 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7C7NSo14857 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sat, 12 Aug 2000 09:23:30 +0200 (MET DST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) id e7C7N3R38638; Sat, 12 Aug 2000 09:23:03 +0200 (CEST) Date: Sat, 12 Aug 2000 09:23:02 +0200 From: Bernd Walter To: Joe Modjeski Cc: "'freebsd-scsi@freebsd.org'" Subject: Re: to Vinum or not to Vinum Message-ID: <20000812092302.A38500@cicely7.cicely.de> References: <00101B7A7FDDD311A89500A0CC56C79048B0@MS1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <00101B7A7FDDD311A89500A0CC56C79048B0@MS1>; from jmodjeski@ms1.northlink.com on Thu, Aug 10, 2000 at 12:09:47PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Aug 10, 2000 at 12:09:47PM -0700, Joe Modjeski wrote: > Currently we have 3 Compaq Proliant 1600R servers with 6 9.1 Ultra3 drives > in each. We are attempting (very unsuccessfully) to do Raid5 with vinum. > We get fatal trap 12 errors very regularly and after a few reboots the vinum > volume is so chewed up that we end up having to rebuild the system. I > tracked down the majority of the problems to the /etc/security script. I > believe it is about the 6th or 7th line down where it starts the find run. > The box starts off fine but after about 1 minute it starts to hit all the > drives at once then BLAM!! It gives me the error. Are your fatal trap 12 errors kernel panics? If yes do you see some SCSI error messages directly before this happens? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 12 13:24:28 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from northlink.com (northlink.com [216.19.0.216]) by hub.freebsd.org (Postfix) with ESMTP id D84A337BA0B for ; Sat, 12 Aug 2000 13:24:14 -0700 (PDT) (envelope-from jmodjeski@ms1.northlink.com) Received: from ms1.northlink.com (ms1.northlink.com [216.19.4.28]) by northlink.com (8.9.1/8.9.1) with ESMTP id NAA26305; Sat, 12 Aug 2000 13:23:57 -0700 (MST) X-Real-From: jmodjeski@ms1.northlink.com X-Real-To: freebsd-scsi@freebsd.org Received: by MS1 with Internet Mail Service (5.5.2650.21) id ; Sat, 12 Aug 2000 13:11:40 -0700 Message-ID: <00101B7A7FDDD311A89500A0CC56C79048B9@MS1> From: Joe Modjeski To: "'Bernd Walter'" Cc: "'freebsd-scsi@freebsd.org'" Subject: RE: to Vinum or not to Vinum Date: Sat, 12 Aug 2000 13:11:39 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thu, Aug 10, 2000 at 12:09:47PM -0700, Joe Modjeski wrote: > > Currently we have 3 Compaq Proliant 1600R servers with 6 > 9.1 Ultra3 drives > > in each. We are attempting (very unsuccessfully) to do > Raid5 with vinum. > > We get fatal trap 12 errors very regularly and after a few > reboots the vinum > > volume is so chewed up that we end up having to rebuild the > system. I > > tracked down the majority of the problems to the > /etc/security script. I > > believe it is about the 6th or 7th line down where it > starts the find run. > > The box starts off fine but after about 1 minute it starts > to hit all the > > drives at once then BLAM!! It gives me the error. > > Are your fatal trap 12 errors kernel panics? > If yes do you see some SCSI error messages directly before > this happens? > > -- > B.Walter COSMO-Project > http://www.cosmo-project.de > ticso@cicely.de Usergroup info@cosmo-project.de > Yes they are kernel panics. And Yes there are always SCSI errors. BAD DSA ( SOME_HEX_NUMBER ) in queue SCSI BUS RESET DETECTED sym0:0:-1:-1 The above isn't exact. The message conveniently misses the logs. I can get the exact messages if you would like. I am trying to avoid crashing the box as much as possible. :) The drives are Hotswap and it does appear that they get "Disconnected" when the error happens. It is however no specific. In my original vinum setup I was spanning the raid across all 6 drives. Then it was consistant with drive 0. I though that was reason for the trouble so I changed the configuration to the one included in the previous message. I have compiled a debug kernel in an effort to get a dump and now the fatal trap 12 kernel panics are less the SCSI errors that go along with them are more consistant. Joe Modjeski Administrator jmodjeski@northlink.com Northlink LLC 450 W Goodwin Suite 107 Phone: (520) 445-0707 Fax: (520) 541-0096 http://www.northlink.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 12 15:20:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 8DF0337BA94 for ; Sat, 12 Aug 2000 15:20:50 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7CMKdB06168 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sun, 13 Aug 2000 00:20:45 +0200 (MET DST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) id e7CMKbd40346; Sun, 13 Aug 2000 00:20:37 +0200 (CEST) Date: Sun, 13 Aug 2000 00:20:37 +0200 From: Bernd Walter To: Joe Modjeski Cc: "'Bernd Walter'" , "'freebsd-scsi@freebsd.org'" Subject: Re: to Vinum or not to Vinum Message-ID: <20000813002036.A40322@cicely7.cicely.de> References: <00101B7A7FDDD311A89500A0CC56C79048B9@MS1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <00101B7A7FDDD311A89500A0CC56C79048B9@MS1>; from jmodjeski@ms1.northlink.com on Sat, Aug 12, 2000 at 01:11:39PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 12, 2000 at 01:11:39PM -0700, Joe Modjeski wrote: > > > On Thu, Aug 10, 2000 at 12:09:47PM -0700, Joe Modjeski wrote: > > > Currently we have 3 Compaq Proliant 1600R servers with 6 > > 9.1 Ultra3 drives > > > in each. We are attempting (very unsuccessfully) to do > > Raid5 with vinum. > > > We get fatal trap 12 errors very regularly and after a few > > reboots the vinum > > > volume is so chewed up that we end up having to rebuild the > > system. I > > > tracked down the majority of the problems to the > > /etc/security script. I > > > believe it is about the 6th or 7th line down where it > > starts the find run. > > > The box starts off fine but after about 1 minute it starts > > to hit all the > > > drives at once then BLAM!! It gives me the error. > > > > Are your fatal trap 12 errors kernel panics? > > If yes do you see some SCSI error messages directly before > > this happens? > > Yes they are kernel panics. And Yes there are always SCSI errors. > > BAD DSA ( SOME_HEX_NUMBER ) in queue > SCSI BUS RESET DETECTED sym0:0:-1:-1 > > The above isn't exact. The message conveniently misses the logs. I can get > the exact messages if you would like. I am trying to avoid crashing the box > as much as possible. :) The exact error including the hex codes is important to distinguish between a bus error or something in the code. > The drives are Hotswap and it does appear that they get "Disconnected" when > the error happens. It is however no specific. In my original vinum setup I > was spanning the raid across all 6 drives. Then it was consistant with > drive 0. I though that was reason for the trouble so I changed the > configuration to the one included in the previous message. > > I have compiled a debug kernel in an effort to get a dump and now the fatal > trap 12 kernel panics are less the SCSI errors that go along with them are > more consistant. You mean you get SCSI errors sometimes without panics directly after? Are you still using the sym controller or is that behavour with the ahc card you mentioned? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 12 21: 7:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from starfire.mn.org (starfire.skypoint.net [199.86.35.134]) by hub.freebsd.org (Postfix) with ESMTP id 383C337BDC5 for ; Sat, 12 Aug 2000 21:07:24 -0700 (PDT) (envelope-from john@starfire.mn.org) Received: (from john@localhost) by starfire.mn.org (8.8.5/1.1) id XAA21754; Sat, 12 Aug 2000 23:07:23 -0500 (CDT) Message-ID: Date: Sat, 12 Aug 2000 23:07:22 -0500 From: john@dexter.starfire.mn.org (John) To: freebsd-scsi@FreeBSD.org Subject: Exabyte vendor-specific commands? X-Mailer: Mutt 0.53 Mime-Version: 1.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a number of tapes written on a Exabyte 8200 which I now wish to reuse on an Exabyte 8500. It works, but they continue to be written in 8200 mode, which doesn't have the density, performance, or QUICK SEEK features that I desire. I have dug around some, and apparently Arcserve has a function called "Quick Erase Plus" which will do this. It must be issuing one (or more) SCSI commands to the drive to accomplish this. If I had those commands, I'm confident of my ability to either use SCSI passthrough or write a custom ioctl to accomplish this. I have written to Exabyte, and though I got an incident number, the silence has been deafening since. Anybody have any light to shed on this one? Thanks! -- John Lind john@starfire.MN.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message