From owner-freebsd-scsi Sun Feb 17 11:20:19 2002 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 49F0B37B404 for ; Sun, 17 Feb 2002 11:20:04 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g1HJJaP91516; Sun, 17 Feb 2002 12:19:36 -0700 (MST) (envelope-from ken) Date: Sun, 17 Feb 2002 12:19:35 -0700 From: "Kenneth D. Merry" To: Ben Neuman Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Issues with ATAPICAM and 4.5-STABLE Message-ID: <20020217121935.A91499@panzer.kdm.org> References: <20020216160043.69a1d4a0.olorin@olorin.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020216160043.69a1d4a0.olorin@olorin.homeip.net>; from olorin@olorin.homeip.net on Sat, Feb 16, 2002 at 04:00:43PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [ Please keep your line lengths less than 80 columns ] On Sat, Feb 16, 2002 at 16:00:43 -0500, Ben Neuman wrote: > I've been trying out the ATAPICAM patch(20020205), and not having much luck with it. After applying the patch, I enabled scbus, da, and ATAPICAM in the kernel. It compiled and installed fine, but I had issues on boot. Here is the output from dmesg: > acd0: DVD-ROM at ata1-master using UDMA66 > acd1: CD-RW at ata1-slave using WDMA2 > (noperiph:atapi1:0:-1:-1): Registered SIM for ata1 > atapicam1m: read data overrun 96/95 > atapicam1s: unknown CMD (0x12) - ILLEGAL REQUEST asc=24 ascq=00 error=04 > atapicam1m: unknown CMD (0x12) - ILLEGAL REQUEST asc=24 ascq=00 error=00 > Mounting root from ufs:/dev/ad0s1a > cd0 at atapi1 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 844.800MB/s transfers (2048bit) > cd0: Attempt to query device size failed: NOT READY, Medium not present > cd1 at atapi1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 844.800MB/s transfers (2048bit) > cd1: Attempt to query device size failed: NOT READY, Medium not present > > It didn't hang, but running cdrecord -scanbus gave me a "No SCSI devices found". You probably haven't enabled the pass device in your kernel config. cdrecord needs to use the pass device to talk to your cdrom. 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 Feb 18 8:10:47 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from leviathan.ele.uri.edu (leviathan.ele.uri.edu [131.128.51.64]) by hub.freebsd.org (Postfix) with ESMTP id 7850A37B400 for ; Mon, 18 Feb 2002 08:10:40 -0800 (PST) Received: from dove (dove.ele.uri.edu [131.128.51.230]) by leviathan.ele.uri.edu (8.11.2/8.11.2) with SMTP id g1IGAZX10341 for ; Mon, 18 Feb 2002 11:10:39 -0500 (EST) Message-ID: <001601c1b896$a96cce90$e6338083@dove> From: "Xubin(Ben) He" To: Subject: target mode. Date: Mon, 18 Feb 2002 11:09:32 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01C1B86C.BE2C0820" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0013_01C1B86C.BE2C0820 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I am trying to configure target mode under FreeBSD 4.5. The SCSI = adapter is Adpatec 39160. I have a IBM SCSI disk connected to Channel A, = id 1. The Adapter ID is set to 5. What I want to do is configure this = adapter unning in target mode. I did it as follows: 1. add device targ, targbh, and options AHC_TMODE_ENABLE=3D0x01 as Jacob = mentioned. 2. When I tried to add "options AHC_TARGET_MODE" in my conf file, I got = an error message "unknown option:AHC_TARGET_MODE". So I added a line = "define AHC_TARGET_MODE" in file aic7xxx.h as alternatives. 3. Recompile the new kernel. 4. Reboot the new kernel, I did see the following message: (targbh0:ahc0:0:-1:-1):lun now enabled for target mode 5. sh MAKEDEV targ0 5. But when I tried to run /usr/sahre/examples/scsi_target/scsi_target = -p 0 -t 1 -l 0 I got the following messages: Configuring Target Mode targ0:ahc0:0:1:0: Lun now enabled for target mode TARGIODEBUG:Inappropriate ioctl for device targetfreeinstance:Unexpected CAM STATUS 5 targ0:ahc0:0:1:0: target mode disabled configuring Initiator Mode =20 I tried many other combinations, but the target mdoe still did not work. = Could anybody point out what's the problem or anything I did wrong?Many = thanks. ----------Ben ------=_NextPart_000_0013_01C1B86C.BE2C0820 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
        I = am trying=20 to configure target mode under FreeBSD 4.5. The SCSI adapter is Adpatec = 39160. I=20 have a IBM SCSI disk connected to Channel A, id 1. The Adapter ID is set = to 5.=20 What I want to do is configure this adapter unning in target mode. I did = it as=20 follows:
1. add device targ, targbh, and options = AHC_TMODE_ENABLE=3D0x01 as Jacob mentioned.
2. When I tried to add "options = AHC_TARGET_MODE" in=20 my conf file, I got an error message "unknown option:AHC_TARGET_MODE". = So I=20 added a line "define AHC_TARGET_MODE" in file aic7xxx.h as=20 alternatives.
3. Recompile the new = kernel.
4. Reboot the new kernel, I did see the = following=20 message:
       =20 (targbh0:ahc0:0:-1:-1):lun now enabled for target mode
5. sh MAKEDEV targ0
5. But when I tried to run=20 /usr/sahre/examples/scsi_target/scsi_target -p 0 -t 1 -l 0 I got the = following=20 messages:
        = Configuring=20 Target Mode
       =20 targ0:ahc0:0:1:0: Lun now enabled for target mode
       =20 TARGIODEBUG:Inappropriate ioctl for device
       =20 targetfreeinstance:Unexpected CAM  STATUS 5
       =20 targ0:ahc0:0:1:0: target mode disabled
        = configuring=20 Initiator Mode
        =
I tried many other combinations, but = the target=20 mdoe still did not work. Could anybody point out what's the problem or = anything=20 I did wrong?Many thanks.
----------Ben
------=_NextPart_000_0013_01C1B86C.BE2C0820-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 18 8:18:54 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 9790E37B427 for ; Mon, 18 Feb 2002 08:18:34 -0800 (PST) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id g1IGIYf08131 for ; Mon, 18 Feb 2002 08:18:34 -0800 (PST) (envelope-from mjacob@feral.com) Date: Mon, 18 Feb 2002 08:18:34 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: scsi@freebsd.org Subject: SCSI target mode. (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Some nincompoop went to a great deal of effort to ask a question via email that cannot possibly be replied to. In any case, it's for the Adaptec HBA, not QLogic. I'm forwarding it here in case this nimrod reads the lists and realizes that this forum would have been a better place to ask the question to begin with. ---------- Forwarded message ---------- Return-Path: Received: from cocoja.holywar.net (socks5@cocoja.holywar.net [211.239.166.202]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id g1IGFBf08103 for ; Mon, 18 Feb 2002 08:15:12 -0800 (PST) (envelope-from nobody@cocoja.holywar.net) Received: (from nobody@localhost) by cocoja.holywar.net (8.11.6/8.11.4) id g1IGF9001164; Tue, 19 Feb 2002 01:15:09 +0900 (KST) (envelope-from nobody) Date: Tue, 19 Feb 2002 01:15:09 +0900 (KST) Message-Id: <200202181615.g1IGF9001164@cocoja.holywar.net> From: "Ben" <> To: "Matthew Jacob" Reply-To: "Ben" <> Subject: SCSI target mode. Organization: HolyNet X-Mailer: HolyBoard 2000 (FRD3xIMY-1.0) Dear Mr. Jacob, I am trying to configure target mode under FreeBSD 4.5. The SCSI adapter is Adpatec 39160. I have a IBM SCSI disk connected to Channel A, id 1. The Adapter ID is set to 5. What I want to do is configure this adapter unning in target mode. I did it as follows: 1. add device targ, targbh, and options AHC_TMODE_ENABLE=0x01 as Jacob mentioned. 2. When I tried to add "options AHC_TARGET_MODE" in my conf file, I got an error message "unknown option:AHC_TARGET_MODE". So I added a line "define AHC_TARGET_MODE" in file aic7xxx.h as alternatives. 3. Recompile the new kernel. 4. Reboot the new kernel, I did see the following message: (targbh0:ahc0:0:-1:-1):lun now enabled for target mode 5. sh MAKEDEV targ0 5. But when I tried to run /usr/sahre/examples/scsi_target/scsi_target -p 0 -t 1 -l 0 I got the following messages: Configuring Target Mode targ0:ahc0:0:1:0: Lun now enabled for target mode TARGIODEBUG:Inappropriate ioctl for device targetfreeinstance:Unexpected CAM STATUS 5 targ0:ahc0:0:1:0: target mode disabled configuring Initiator Mode I tried many other combinations, but the target mdoe still did not work. Could you point out what's the problem or anything I did wrong?Many thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 19 5:26:59 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rigel.grass.st (rigel.grass.st [195.197.32.30]) by hub.freebsd.org (Postfix) with ESMTP id 20E1B37B416 for ; Tue, 19 Feb 2002 05:26:54 -0800 (PST) Received: (from bsdscsi@localhost) by rigel.grass.st (8.9.3/8.9.3) id PAA25410 for scsi@freebsd.org; Tue, 19 Feb 2002 15:26:52 +0200 (EET) (envelope-from bsdscsi) Date: Tue, 19 Feb 2002 15:26:52 +0200 From: mika ruohotie To: scsi@freebsd.org Subject: ASUS P2B-DS unable to boot 4.5 or 5.0-20020218 from floppies Message-ID: <20020219152652.A25402@rigel.grass.st> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org as the subject says... i have the said motherboard and i am totally unable to boot either one of those operating systems (from floppies) on that hardware. it doesnt matter if i leave the onboard scsi unused, it's still unable to boot. i also tested the USB behaviour suggested on some mailing list (i forgot which one, i searched the keywords from many lists). anyone with suggestions, or preferably idea what's broken. yes, the said hardware used to run freebsd, at least current from early summer works, also possibly 4.2 (someone else said 4.2 would work, on some mailinglist). what i understand, it's some kind of scsi hang, caused by ahc, since it's looping and tells me someone reset the scsi-bus (which is sitting without disks, with disks it just hangs, no difference if i have just terminators on it or not) i'll mail this to scsi, since it's more about scsi than hardware. mickey -- mika ruohotie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 19 21:18:27 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.sat.t.u-tokyo.ac.jp (nat.keisu.t.u-tokyo.ac.jp [133.11.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 9AA4C37B404 for ; Tue, 19 Feb 2002 21:18:22 -0800 (PST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by mail.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id D772C2DABB; Wed, 20 Feb 2002 14:18:21 +0900 (JST) Date: Wed, 20 Feb 2002 14:18:21 +0900 Message-ID: From: Hidetoshi Shimokawa To: freebsd-scsi@freebsd.org Cc: Katsushi Kobayashi Subject: RBC support patch User-Agent: Wanderlust/2.4.1 (Stand By Me) REMI/1.14.3 (Matsudai) FLIM/1.13.2 (Kasanui) APEL/10.3 MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm developing firewire/SBP driver with kobayashi-san and We need RBC support in SCSI layer. Here is a patch for RBC. Can I commit this to current or could someone commit? Another issue, there are many broken 'Direct Access' devices which don't support 'READ(6)/WRITE(6)' operations. You can see tons of quirks in scsi_da.c for that. Why don't we set minimum_cmd_size as 10 by default? Old drivers doesn't have READ(10)/WRITE(10) ? /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html Index: scsi/scsi_all.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v retrieving revision 1.28 diff -u -r1.28 scsi_all.c --- scsi/scsi_all.c 6 Nov 2001 23:50:33 -0000 1.28 +++ scsi/scsi_all.c 18 Feb 2002 13:13:56 -0000 @@ -2220,6 +2220,12 @@ case T_ENCLOSURE: dtype = "Enclosure Services"; break; + case T_RBC: + dtype = "Simplified Direct Access"; + break; + case T_OCRW: + dtype = "Optical Card Read/Write"; + break; case T_NODEVICE: dtype = "Uninstalled"; default: Index: scsi/scsi_da.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v retrieving revision 1.96 diff -u -r1.96 scsi_da.c --- scsi/scsi_da.c 31 Jan 2002 11:39:16 -0000 1.96 +++ scsi/scsi_da.c 18 Feb 2002 13:51:49 -0000 @@ -1025,6 +1039,7 @@ break; if (SID_TYPE(&cgd->inq_data) != T_DIRECT + && SID_TYPE(&cgd->inq_data) != T_RBC && SID_TYPE(&cgd->inq_data) != T_OPTICAL) break; @@ -1124,7 +1139,7 @@ else softc->quirks = DA_Q_NONE; - if (softc->quirks & DA_Q_NO_6_BYTE) + if (softc->quirks & DA_Q_NO_6_BYTE || SID_TYPE(&cgd->inq_data) == T_RBC) softc->minimum_cmd_size = 10; else softc->minimum_cmd_size = 6; /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 11:41:47 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 9837D37B48D for ; Wed, 20 Feb 2002 11:40:06 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA01056 for freebsd-scsi@freebsd.org; Wed, 20 Feb 2002 20:40:05 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1KJaAO07448; Wed, 20 Feb 2002 20:36:10 +0100 (MET) (envelope-from j) Date: Wed, 20 Feb 2002 20:36:10 +0100 (MET) Message-Id: <200202201936.g1KJaAO07448@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: RBC support patch X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hidetoshi Shimokawa wrote: > Another issue, there are many broken 'Direct Access' devices which > don't support 'READ(6)/WRITE(6)' operations. They are not broken. READ(6)/WRITE(6) are not mandatory for direct access devices by the standard, but READ(10)/WRITE(10) are. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 12:39:40 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 1081437B416 for ; Wed, 20 Feb 2002 12:39:38 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220203930.MLMN2626.rwcrmhc51.attbi.com@gateway.posi.net>; Wed, 20 Feb 2002 20:39:30 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1KKdTG86165; Wed, 20 Feb 2002 12:39:29 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Wed, 20 Feb 2002 12:39:28 -0800 (PST) From: Kelly Yancey To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch In-Reply-To: <200202201936.g1KJaAO07448@uriah.heep.sax.de> Message-ID: <20020220123457.Y86103-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Feb 2002, Joerg Wunsch wrote: > Hidetoshi Shimokawa wrote: > > > Another issue, there are many broken 'Direct Access' devices which > > don't support 'READ(6)/WRITE(6)' operations. > > They are not broken. READ(6)/WRITE(6) are not mandatory for direct > access devices by the standard, but READ(10)/WRITE(10) are. > > -- > cheers, J"org .-.-. --... ...-- -.. . DL8DTL Unfortunately, my copy of the SCSI-2 draft lists READ(10) and WRITE(10) as optional for direct-access devices. Otherwise, this would be an easy fix to a long standing annoyance. :| Kelly kbyanc@{posi.net,FreeBSD.org} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 13:40:14 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id CB56B37B417 for ; Wed, 20 Feb 2002 13:40:06 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id WAA02473; Wed, 20 Feb 2002 22:40:03 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1KLVO309627; Wed, 20 Feb 2002 22:31:24 +0100 (MET) (envelope-from j) Date: Wed, 20 Feb 2002 22:31:24 +0100 From: Joerg Wunsch To: Kelly Yancey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch Message-ID: <20020220223124.A9579@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , Kelly Yancey , freebsd-scsi@FreeBSD.ORG References: <200202201936.g1KJaAO07448@uriah.heep.sax.de> <20020220123457.Y86103-100000@gateway.posi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020220123457.Y86103-100000@gateway.posi.net>; from kbyanc@posi.net on Wed, Feb 20, 2002 at 12:39:28PM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Kelly Yancey wrote: > > They are not broken. READ(6)/WRITE(6) are not mandatory for direct > > access devices by the standard, but READ(10)/WRITE(10) are. > Unfortunately, my copy of the SCSI-2 draft lists READ(10) and > WRITE(10) as optional for direct-access devices. Otherwise, this > would be an easy fix to a > long standing annoyance. :| Hmm, after reading the docs again, i have to correct myself: both are mandatory, either by my SCSI-2 copy as well as by the SCSI-3 drafts i've got. The latter contain a footnote explaining that the 6-byte commands have been kept as `mandatory' since some boot environments require it, while applications are requested to migrate to the 10-byte commands. So perhaps we should simply reverse the logic, use the 10-byte opcodes as default, and collect the list of (too old) devices that require the 6-byte CDBs. How does that sound? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 13:57:45 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 05E7137B402 for ; Wed, 20 Feb 2002 13:57:39 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220215738.TMZF1147.rwcrmhc52.attbi.com@gateway.posi.net>; Wed, 20 Feb 2002 21:57:38 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1KLvXf86397; Wed, 20 Feb 2002 13:57:33 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Wed, 20 Feb 2002 13:57:32 -0800 (PST) From: Kelly Yancey To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch In-Reply-To: <20020220223124.A9579@uriah.heep.sax.de> Message-ID: <20020220134946.X86372-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Feb 2002, Joerg Wunsch wrote: > As Kelly Yancey wrote: > > > > They are not broken. READ(6)/WRITE(6) are not mandatory for direct > > > access devices by the standard, but READ(10)/WRITE(10) are. > > > Unfortunately, my copy of the SCSI-2 draft lists READ(10) and > > WRITE(10) as optional for direct-access devices. Otherwise, this > > would be an easy fix to a > > long standing annoyance. :| > > Hmm, after reading the docs again, i have to correct myself: both > are mandatory, either by my SCSI-2 copy as well as by the SCSI-3 > drafts i've got. The latter contain a footnote explaining that the > 6-byte commands have been kept as `mandatory' since some boot > environments require it, while applications are requested to migrate to > the 10-byte commands. > > So perhaps we should simply reverse the logic, use the 10-byte opcodes > as default, and collect the list of (too old) devices that require the > 6-byte CDBs. How does that sound? > > -- > cheers, J"org .-.-. --... ...-- -.. . DL8DTL You are right, SCSI 3 lists both 6 and 10-byte READ/WRITE commands are mandatory. However, SCSI 2 lists both as optional. So we could just key off the INQUIRY results and if the device reports itself as SCSI3 or newer force 10 byte commands, otherwise keep using 6 byte commands. Sounds reasonable to me. What will be interesting is seeing if this would fix all the SCSI->USB quirks along the way (i.e. do they report themselves as SCSI3 conforming?). I'll make up a quick patch and post it for review shortly. Kelly kbyanc@{posi.net,FreeBSD.org} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 15:17:11 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 30E2E37B400 for ; Wed, 20 Feb 2002 15:17:08 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220231707.WBVR1214.rwcrmhc54.attbi.com@gateway.posi.net>; Wed, 20 Feb 2002 23:17:07 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1KNH6m86612; Wed, 20 Feb 2002 15:17:07 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Wed, 20 Feb 2002 15:17:06 -0800 (PST) From: Kelly Yancey To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch In-Reply-To: <20020220134946.X86372-100000@gateway.posi.net> Message-ID: <20020220151340.V86607-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Feb 2002, Kelly Yancey wrote: > You are right, SCSI 3 lists both 6 and 10-byte READ/WRITE commands are > mandatory. However, SCSI 2 lists both as optional. So we could just key off > the INQUIRY results and if the device reports itself as SCSI3 or newer force > 10 byte commands, otherwise keep using 6 byte commands. Sounds reasonable to > me. > What will be interesting is seeing if this would fix all the SCSI->USB > quirks along the way (i.e. do they report themselves as SCSI3 conforming?). > > I'll make up a quick patch and post it for review shortly. > > Kelly [replying to self] Here is a quick patch that should do the trick. I haven't tested it yet, though (it's pretty straightforward) as I have to wait for my current box to rebuild. Kelly kbyanc@{posi.net,FreeBSD.org} P.S. In theory we could add a warning if a quirk containing only DA_Q_NO_6_BYTE is found and the device reports itself as SCSI3 alerting us that we can safely remove the quirk. Index: scsi_da.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v retrieving revision 1.97 diff -u -r1.97 scsi_da.c --- scsi_da.c 18 Feb 2002 13:35:30 -0000 1.97 +++ scsi_da.c 20 Feb 2002 23:13:32 -0000 @@ -1131,7 +1131,8 @@ else softc->quirks = DA_Q_NONE; - if (softc->quirks & DA_Q_NO_6_BYTE) + if ((softc->quirks & DA_Q_NO_6_BYTE) || + (SID_ANSI_REV(&cgd->inq_data) >= SCSI_REV_3)) softc->minimum_cmd_size = 10; else softc->minimum_cmd_size = 6; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 15:19:46 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 9D09737B402 for ; Wed, 20 Feb 2002 15:19:43 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g1KNJkI40066; Wed, 20 Feb 2002 16:19:46 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200202202319.g1KNJkI40066@aslan.scsiguy.com> To: Kelly Yancey Cc: Joerg Wunsch , freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch In-Reply-To: Your message of "Wed, 20 Feb 2002 13:57:32 PST." <20020220134946.X86372-100000@gateway.posi.net> Date: Wed, 20 Feb 2002 16:19:46 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > What will be interesting is seeing if this would fix all the SCSI->USB >quirks along the way (i.e. do they report themselves as SCSI3 conforming?). > > I'll make up a quick patch and post it for review shortly. We should adjust dynamically. This really shouldn't be too hard to do. Then all of the black list items go away. I'll see about whipping up a patch for this. It's been going on for too long and my prodding at others to do the work hasn't been successful, so I'll just go do it. 8-) -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 15:34:37 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 0462737B41E for ; Wed, 20 Feb 2002 15:34:15 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220233415.VLYI2951.rwcrmhc53.attbi.com@gateway.posi.net>; Wed, 20 Feb 2002 23:34:15 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1KNYE086674; Wed, 20 Feb 2002 15:34:15 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Wed, 20 Feb 2002 15:34:13 -0800 (PST) From: Kelly Yancey To: "Justin T. Gibbs" Cc: Joerg Wunsch , Subject: Re: RBC support patch In-Reply-To: <200202202319.g1KNJkI40066@aslan.scsiguy.com> Message-ID: <20020220152807.F86607-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Feb 2002, Justin T. Gibbs wrote: > > What will be interesting is seeing if this would fix all the SCSI->USB > >quirks along the way (i.e. do they report themselves as SCSI3 conforming?). > > > > I'll make up a quick patch and post it for review shortly. > > We should adjust dynamically. This really shouldn't be too hard > to do. Then all of the black list items go away. I'll see about > whipping up a patch for this. It's been going on for too long and > my prodding at others to do the work hasn't been successful, so I'll > just go do it. 8-) > > -- > Justin What do you mean by "adjust dynamically"? Are you proposing to convert 6 byte commands to 10 byte commands once the 6 byte version fails? If so, I could easily whip that up later this afternoon as jhb already added this functionality to umass a while back; it just needs to be moved to scsi_da. However, I thought this was frowned upon for some reason. Kelly kbyanc@{posi.net,FreeBSD.org} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 15:59:35 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id DAB8537B417 for ; Wed, 20 Feb 2002 15:59:33 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g1KNxeI41069; Wed, 20 Feb 2002 16:59:40 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200202202359.g1KNxeI41069@aslan.scsiguy.com> To: Kelly Yancey Cc: Joerg Wunsch , freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch In-Reply-To: Your message of "Wed, 20 Feb 2002 15:34:13 PST." <20020220152807.F86607-100000@gateway.posi.net> Date: Wed, 20 Feb 2002 16:59:40 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > What do you mean by "adjust dynamically"? If a 6 byte command fails with "command not supported", switch to 10 byte commands, and retry the current transaction. As far as I know, the devices do return a proper response. Those that don't, we will still have to black list. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 20 16:35:16 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id F2A9137B402 for ; Wed, 20 Feb 2002 16:35:13 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020221003513.XFFW2951.rwcrmhc53.attbi.com@gateway.posi.net>; Thu, 21 Feb 2002 00:35:13 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1L0ZCl86804; Wed, 20 Feb 2002 16:35:12 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Wed, 20 Feb 2002 16:35:12 -0800 (PST) From: Kelly Yancey To: "Justin T. Gibbs" Cc: Joerg Wunsch , Subject: Re: RBC support patch In-Reply-To: <200202202359.g1KNxeI41069@aslan.scsiguy.com> Message-ID: <20020220163421.K86749-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Feb 2002, Justin T. Gibbs wrote: > > What do you mean by "adjust dynamically"? > > If a 6 byte command fails with "command not supported", switch to > 10 byte commands, and retry the current transaction. As far as I > know, the devices do return a proper response. Those that don't, > we will still have to black list. > Easy enough. I'll see if I can't get you patches for review tomorrow. Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 2:31:39 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp2.flashnet.it (smtp2.flashnet.it [194.247.160.60]) by hub.freebsd.org (Postfix) with ESMTP id 3120737B417 for ; Thu, 21 Feb 2002 02:31:35 -0800 (PST) Received: from smtp.flashnet.it (ip009.pool-173.cyb.it [195.191.181.10]) by smtp2.flashnet.it (8.10.2/8.10.2) with SMTP id g1LBcAB28723 for ; Thu, 21 Feb 2002 11:38:10 GMT Message-Id: <200202211138.g1LBcAB28723@smtp2.flashnet.it> To: freebsd-scsi@freebsd.org X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Thu, 21 Feb 2002 11:31:33 EST From: Andrea Venturoli Reply-To: Andrea Venturoli Subject: sym0:0: message d sent on bad reselection. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello there. I got a file server who > Feb 20 07:22:24 david /kernel: sym0:0: message d sent on bad reselection. Then I see no other line in log until the machine was cycle powered. Obviously enough fsck -p at boot failed and I had to run fsck manually (ok, I know about fsck_y_enable...). What could the above line mean? I tried searching the mailing list archives, but basically found nothing useful. The sym driver's man page and sources weren't of much help either. bye & Thanks av. P.S. Plese answer to my e-mail also. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 3:56:34 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.sat.t.u-tokyo.ac.jp (nat.keisu.t.u-tokyo.ac.jp [133.11.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 058EE37B400 for ; Thu, 21 Feb 2002 03:56:31 -0800 (PST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by mail.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id DF3532DC74; Thu, 21 Feb 2002 20:56:29 +0900 (JST) Date: Thu, 21 Feb 2002 20:56:29 +0900 Message-ID: From: Hidetoshi Shimokawa To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-scsi@FreeBSD.ORG, "Justin T. Gibbs" Subject: Re: RBC support patch In-Reply-To: <200202201936.g1KJaAO07448@uriah.heep.sax.de> References: <200202201936.g1KJaAO07448@uriah.heep.sax.de> <200202202359.g1KNxeI41069@aslan.scsiguy.com> User-Agent: Wanderlust/2.4.1 (Stand By Me) REMI/1.14.3 (Matsudai) FLIM/1.13.2 (Kasanui) APEL/10.3 MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At Wed, 20 Feb 2002 20:36:10 +0100 (MET), Joerg Wunsch wrote: > > Hidetoshi Shimokawa wrote: > > > Another issue, there are many broken 'Direct Access' devices which > > don't support 'READ(6)/WRITE(6)' operations. > > They are not broken. READ(6)/WRITE(6) are not mandatory for direct > access devices by the standard, but READ(10)/WRITE(10) are. If this was true, FreeBSD is broken X-) At Wed, 20 Feb 2002 16:59:40 -0700, Justin T. Gibbs wrote: > > > What do you mean by "adjust dynamically"? > > If a 6 byte command fails with "command not supported", switch to > 10 byte commands, and retry the current transaction. As far as I > know, the devices do return a proper response. Those that don't, > we will still have to black list. > > -- > Justin This seems right way to go. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 4:30:32 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 8641537B416 for ; Thu, 21 Feb 2002 04:30:15 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id NAA13459; Thu, 21 Feb 2002 13:30:07 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1LCQIA26514; Thu, 21 Feb 2002 13:26:18 +0100 (MET) (envelope-from j) Date: Thu, 21 Feb 2002 13:26:18 +0100 From: Joerg Wunsch To: Hidetoshi Shimokawa Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch Message-ID: <20020221132618.A26495@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , Hidetoshi Shimokawa , freebsd-scsi@FreeBSD.ORG References: <200202201936.g1KJaAO07448@uriah.heep.sax.de> <200202202359.g1KNxeI41069@aslan.scsiguy.com> <200202201936.g1KJaAO07448@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from simokawa@sat.t.u-tokyo.ac.jp on Thu, Feb 21, 2002 at 08:56:29PM +0900 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Hidetoshi Shimokawa wrote: > > They are not broken. READ(6)/WRITE(6) are not mandatory for direct > > access devices by the standard, but READ(10)/WRITE(10) are. > > If this was true, FreeBSD is broken X-) No, see my followup. Both READ(6) and READ(10) are mandatory, even in SCSI-2. I've obviously confused this with WRITE(6) and WRITE(10) which are both optional. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 6:58:48 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.sat.t.u-tokyo.ac.jp (nat.keisu.t.u-tokyo.ac.jp [133.11.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 4F7A137B400 for ; Thu, 21 Feb 2002 06:58:43 -0800 (PST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by mail.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id D90F42DABD; Thu, 21 Feb 2002 23:58:41 +0900 (JST) Date: Thu, 21 Feb 2002 23:58:41 +0900 Message-ID: From: Hidetoshi Shimokawa To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: READ_6 patch (Re: RBC support patch) Newsgroups: freebsd.scsi In-Reply-To: References: <200202201936.g1KJaAO07448@uriah.heep.sax.de> <200202202359.g1KNxeI41069@aslan.scsiguy.com> User-Agent: Wanderlust/2.4.1 (Stand By Me) REMI/1.14.3 (Matsudai) FLIM/1.13.2 (Kasanui) APEL/10.3 MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At Thu, 21 Feb 2002 20:56:29 +0900, Hidetoshi Shimokawa wrote: > At Wed, 20 Feb 2002 16:59:40 -0700, > Justin T. Gibbs wrote: > > > > > What do you mean by "adjust dynamically"? > > > > If a 6 byte command fails with "command not supported", switch to > > 10 byte commands, and retry the current transaction. As far as I > > know, the devices do return a proper response. Those that don't, > > we will still have to black list. > > > > -- > > Justin > > This seems right way to go. How about this? Could you review this patch? /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html Index: scsi/scsi_da.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v retrieving revision 1.97 diff -u -r1.97 scsi_da.c --- scsi/scsi_da.c 18 Feb 2002 13:35:30 -0000 1.97 +++ scsi/scsi_da.c 21 Feb 2002 14:47:03 -0000 @@ -1308,6 +1324,22 @@ } } +static void +cmd6to10(struct ccb_scsiio *csio) +{ + struct scsi_rw_6 cmd6; + struct scsi_rw_10 *cmd10; + + bcopy(&csio->cdb_io.cdb_bytes, &cmd6, sizeof(struct scsi_rw_6)); + cmd10 = (struct scsi_rw_10 *) &csio->cdb_io.cdb_bytes; + cmd10->opcode = (cmd6.opcode == READ_6) ? READ_10 : WRITE_10; + cmd10->byte2 = 0; + scsi_ulto4b(scsi_3btoul(cmd6.addr), cmd10->addr); + cmd10->reserved = 0; + scsi_ulto2b(cmd6.length, cmd10->length); + cmd10->control = cmd6.control; + csio->cdb_len = sizeof(*cmd10); +} static void dadone(struct cam_periph *periph, union ccb *done_ccb) @@ -1328,12 +1360,37 @@ int error; int s; int sf; + u_int8_t opcode; if ((csio->ccb_h.ccb_state & DA_CCB_RETRY_UA) != 0) sf = SF_RETRY_UA; else sf = 0; + /* XXX + * Work around for broken direct access device + * which doesn't support READ(6)/WRITE(6). + */ + opcode = ((struct scsi_rw_6 *) + &csio->cdb_io.cdb_bytes)->opcode; + if (opcode == READ_6 || opcode == WRITE_6) { + int sense_key, error_code; + int asc, ascq; + scsi_extract_sense(&csio->sense_data, + &error_code, + &sense_key, + &asc, &ascq); + if (sense_key == SSD_KEY_ILLEGAL_REQUEST) { + printf( + "READ(6)/WRITE(6) failed, " + "minimum_cmd_size is " + "increased to 10.\n"); + softc->minimum_cmd_size = 10; + cmd6to10(csio); + done_ccb->ccb_h.status = + CAM_REQUEUE_REQ; + } + } error = daerror(done_ccb, CAM_RETRY_SELTO, sf); if (error == ERESTART) { /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 11: 1:44 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 94F9A37B400 for ; Thu, 21 Feb 2002 11:01:36 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g1LJ1nI48461; Thu, 21 Feb 2002 12:01:50 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200202211901.g1LJ1nI48461@aslan.scsiguy.com> To: Hidetoshi Shimokawa Cc: freebsd-scsi@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: READ_6 patch (Re: RBC support patch) In-Reply-To: Your message of "Thu, 21 Feb 2002 23:58:41 +0900." Date: Thu, 21 Feb 2002 12:01:49 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> This seems right way to go. > >How about this? >Could you review this patch? Close. Perform the test inside daerror(). Daerror is supposed to filter out any errors specific to the da driver prior to calling the generic error routine, so this is the place to handle this. You should also only need to do the filtering if the ccb has an error flagged in its ccb header. This should avoid any unecessary work on transactions that haven't failed. Lastly, you need to actually requeue the transaction (xpt_action() followed by a release of the device queue if the transaction was marked as having frozen the queue). Thanks for looking into this! -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 11:14:26 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 4CC6D37B400 for ; Thu, 21 Feb 2002 11:14:22 -0800 (PST) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id LAA01758; Thu, 21 Feb 2002 11:12:51 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id KAA16097; Thu, 21 Feb 2002 10:55:32 -0800 (PST) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id MAA15558; Thu, 21 Feb 2002 12:12:48 -0700 (MST) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id <1TZTVY72>; Thu, 21 Feb 2002 12:12:49 -0700 Message-ID: From: "Long, Scott" To: "'Justin T. Gibbs'" , Hidetoshi Shimokawa Cc: freebsd-scsi@freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: RE: READ_6 patch (Re: RBC support patch) Date: Thu, 21 Feb 2002 12:12:48 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Also, after the 6 byte command has failed and been retried successfully as a 10 byte command, should the driver be flagged that all future commands use the 10 byte form? Scott > -----Original Message----- > From: Justin T. Gibbs [mailto:gibbs@scsiguy.com] > Sent: Thursday, February 21, 2002 11:02 AM > To: Hidetoshi Shimokawa > Cc: freebsd-scsi@freebsd.org; joerg_wunsch@uriah.heep.sax.de > Subject: Re: READ_6 patch (Re: RBC support patch) > > > >> This seems right way to go. > > > >How about this? > >Could you review this patch? > > Close. Perform the test inside daerror(). Daerror is > supposed to filter > out any errors specific to the da driver prior to calling the generic > error routine, so this is the place to handle this. You > should also only > need to do the filtering if the ccb has an error flagged in its ccb > header. This should avoid any unecessary work on transactions that > haven't failed. Lastly, you need to actually requeue the transaction > (xpt_action() followed by a release of the device queue if > the transaction > was marked as having frozen the queue). > > Thanks for looking into this! > > -- > Justin > > 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 Thu Feb 21 11:18:45 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id C4B5937B484 for ; Thu, 21 Feb 2002 11:18:02 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g1LJGnI48790; Thu, 21 Feb 2002 12:16:49 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200202211916.g1LJGnI48790@aslan.scsiguy.com> To: "Long, Scott" Cc: Hidetoshi Shimokawa , freebsd-scsi@freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: READ_6 patch (Re: RBC support patch) In-Reply-To: Your message of "Thu, 21 Feb 2002 12:12:48 MST." Date: Thu, 21 Feb 2002 12:16:49 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Also, after the 6 byte command has failed and been retried successfully as a >10 byte command, should the driver be flagged that all future commands use >the 10 byte form? That was included in the original patch. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 12:42:46 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from smtpzilla5.xs4all.nl (smtpzilla5.xs4all.nl [194.109.127.141]) by hub.freebsd.org (Postfix) with ESMTP id 2FD6A37B400 for ; Thu, 21 Feb 2002 12:42:29 -0800 (PST) Received: from discworld (morla.xs4all.nl [213.84.152.233]) by smtpzilla5.xs4all.nl (8.12.0/8.12.0) with SMTP id g1LKgQxO028740 for ; Thu, 21 Feb 2002 21:42:27 +0100 (CET) Reply-To: From: "Roelf Schreurs" To: Subject: scsi raid Date: Thu, 21 Feb 2002 21:41:03 +0100 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sorry, not just scsi but raid question. I'm looking for software to control the RAID configuration on a FreeBSD 4.4 server. It's a DELL Poerwedge 2500. Are there anything like that? Than ks ------------------------------------------------------------- Roelf Schreurs Linux is like a wigwam - no windows, no gates, apache inside! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 13:27:24 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 17D4B37B402 for ; Thu, 21 Feb 2002 13:27:18 -0800 (PST) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id NAA20658; Thu, 21 Feb 2002 13:26:57 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id NAA04943; Thu, 21 Feb 2002 13:09:38 -0800 (PST) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA16766; Thu, 21 Feb 2002 14:26:55 -0700 (MST) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id <1TZTVZDZ>; Thu, 21 Feb 2002 14:26:56 -0700 Message-ID: From: "Long, Scott" To: "'roelf.schreurs@imc.nl'" , freebsd-scsi@freebsd.org Subject: RE: scsi raid Date: Thu, 21 Feb 2002 14:26:54 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, You email is a little vague, so forgive me for asking a lot of questions here. Are you using the onboard RAID? If so, the FreeBSD aac driver should automatically detect it and allow access to your arrays. For management software, you have two choices. The Linux managment tool, afacli, should work fine under FreeBSD's Linux emulation layer. Let me know if you need help with this. The second option is to sit tight for a few more days until Adaptec makes the FreeBSD-native management software available. Scott > -----Original Message----- > From: Roelf Schreurs [mailto:rosc@imc.nl] > Sent: Thursday, February 21, 2002 12:41 PM > To: freebsd-scsi@freebsd.org > Subject: scsi raid > > > Sorry, not just scsi but raid question. > I'm looking for software to control the RAID configuration on > a FreeBSD 4.4 > server. > It's a DELL Poerwedge 2500. > > Are there anything like that? > Than ks > > ------------------------------------------------------------- > > Roelf Schreurs > > Linux is like a wigwam - no windows, no gates, apache inside! > > > 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 Thu Feb 21 14: 0:34 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 4E72637B41A for ; Thu, 21 Feb 2002 14:00:11 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id XAA21978; Thu, 21 Feb 2002 23:00:05 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1LLqO337151; Thu, 21 Feb 2002 22:52:24 +0100 (MET) (envelope-from j) Date: Thu, 21 Feb 2002 22:52:24 +0100 From: Joerg Wunsch To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: Kelly Yancey , freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch Message-ID: <20020221225224.B34036@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , =?iso-8859-1?Q?G=E9rard_Roudier?= , Kelly Yancey , freebsd-scsi@FreeBSD.ORG References: <20020220134946.X86372-100000@gateway.posi.net> <20020220233627.M2119-100000@gerard> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20020220233627.M2119-100000@gerard>; from groudier@free.fr on Wed, Feb 20, 2002 at 11:44:15PM +0100 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Gérard Roudier wrote: > My understanding is that WRITE(10) is just meaningless for read-only > devices, thus optionnal. But this is not worded this way in the > specs. Yep, i thought so, too, after reading the specs a bit more carefully. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 14:12:24 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id BAA4737B402 for ; Thu, 21 Feb 2002 14:12:21 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g1LMCVI52438; Thu, 21 Feb 2002 15:12:31 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200202212212.g1LMCVI52438@aslan.scsiguy.com> To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Kelly Yancey , Joerg Wunsch , freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch In-Reply-To: Your message of "Thu, 21 Feb 2002 00:06:10 +0100." <20020220235751.M2119-100000@gerard> Date: Thu, 21 Feb 2002 15:12:31 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > >This will uselessly run the risk of hurting some direct access devices >that are known to have to support either from specs or just by need >READ(10)/WRITE(10). Then flip the logic (10 then 6). These devices are supposed to report that the command is not supported. All indications I have is that the newer drives do. Older drives just fall of the bus and die if you send a 10byte cdb. >Anyway the *(10) commands are NOT functionnally equivalent to *(10) >function as you know. Right. Look at the code that builds these commands. The smallest command type that can satisfy a given request is used. You can optionally set a minimum command type size too. >May-be you just want to have best possible support for hard disks < 1GB. They work fine now. Why break them? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 14:28:48 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 7B32937B404 for ; Thu, 21 Feb 2002 14:28:43 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020221222843.CGSF1147.rwcrmhc52.attbi.com@gateway.posi.net>; Thu, 21 Feb 2002 22:28:43 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1LMSfF89134; Thu, 21 Feb 2002 14:28:42 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Thu, 21 Feb 2002 14:28:41 -0800 (PST) From: Kelly Yancey To: Joerg Wunsch Cc: =?iso-8859-1?Q?G=E9rard_Roudier?= , Subject: Re: RBC support patch In-Reply-To: <20020221225224.B34036@uriah.heep.sax.de> Message-ID: <20020221140554.N89039-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 21 Feb 2002, Joerg Wunsch wrote: > As G=E9rard Roudier wrote: > > > My understanding is that WRITE(10) is just meaningless for read-only > > devices, thus optionnal. But this is not worded this way in the > > specs. > > Yep, i thought so, too, after reading the specs a bit more carefully. > -- > cheers, J"org .-.-. --... ...-- -.. . DL8DTL I stand corrected: READ(6) and READ(10) are both mandatory in SCSI2. I j= ust eyeballed the WRITE commands (which are both optional) and assumed that applied to READ also. But on second intespection, I see that you are corre= ct. Nonetheless, per Justin's suggestion, I am preparing patches to convert 6 b= yte commands to 10 byte once a device returns 'command not supported' for the 6 byte version. Per recent discussion, I may try and implement 10 to 6 conversion that ma= y be used if the command the DPO, FUA, and RelAdr bits are clear, the transfe= r length is under 256 blocks, and the LBA fits in 21 bits. In which case, if a READ(10) fails, it can fall back to READ(6) (assuming a 6 byte read hasn'= t already failed). In which case, we can determine which size we prefer to t= ry first based on SCSI revision (>=3D2 try 10 byte commands first, <2 try 6 by= te commands first) with fallback should that fail. But note that while 6 to 10 appears fairly straightforward, currently I am only considering converting 10 byte reads to 6 byte reads right now. I'm not too comfortabl= e about the number of restrictions involved to downgrade a later command set = to an earlier one (as demonstrated by the READ criteria I listed above). This is all getting a bit more complicated than I had originally planned. Still doable, it's just going to take me a little longer. Please hold off = on suggesting any more cases/features until I post patches. :) Thanks, Kelly kbyanc@{posi.net,FreeBSD.org} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 15: 8:55 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 2285037B405 for ; Thu, 21 Feb 2002 15:08:51 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020221230850.DHUA1214.rwcrmhc54.attbi.com@gateway.posi.net>; Thu, 21 Feb 2002 23:08:50 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1LN8nk89214; Thu, 21 Feb 2002 15:08:49 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Thu, 21 Feb 2002 15:08:49 -0800 (PST) From: Kelly Yancey To: Joerg Wunsch Cc: =?iso-8859-1?Q?G=E9rard_Roudier?= , Subject: Re: RBC support patch In-Reply-To: <20020221140554.N89039-100000@gateway.posi.net> Message-ID: <20020221150706.C89039-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Argh. Nevermind, it looks like Shimokawa-san is already on the problem. After his patch is committed, maybe then I'll look into 10->6 conversion fo= r READ if anyone still thinks it is necessary. Kelly kbyanc@{posi.net,FreeBSD.org} On Thu, 21 Feb 2002, Kelly Yancey wrote: > On Thu, 21 Feb 2002, Joerg Wunsch wrote: > > > As G=E9rard Roudier wrote: > > > > > My understanding is that WRITE(10) is just meaningless for read-only > > > devices, thus optionnal. But this is not worded this way in the > > > specs. > > > > Yep, i thought so, too, after reading the specs a bit more carefully. > > -- > > cheers, J"org .-.-. --... ...-- -.. . DL8DTL > > I stand corrected: READ(6) and READ(10) are both mandatory in SCSI2. I= just > eyeballed the WRITE commands (which are both optional) and assumed that > applied to READ also. But on second intespection, I see that you are cor= rect. > Nonetheless, per Justin's suggestion, I am preparing patches to convert 6= byte > commands to 10 byte once a device returns 'command not supported' for the= 6 > byte version. > Per recent discussion, I may try and implement 10 to 6 conversion that = may > be used if the command the DPO, FUA, and RelAdr bits are clear, the trans= fer > length is under 256 blocks, and the LBA fits in 21 bits. In which case, = if > a READ(10) fails, it can fall back to READ(6) (assuming a 6 byte read has= n't > already failed). In which case, we can determine which size we prefer to= try > first based on SCSI revision (>=3D2 try 10 byte commands first, <2 try 6 = byte > commands first) with fallback should that fail. But note that while > 6 to 10 appears fairly straightforward, currently I am only considering > converting 10 byte reads to 6 byte reads right now. I'm not too comforta= ble > about the number of restrictions involved to downgrade a later command se= t to > an earlier one (as demonstrated by the READ criteria I listed above). > This is all getting a bit more complicated than I had originally planne= d. > Still doable, it's just going to take me a little longer. Please hold of= f on > suggesting any more cases/features until I post patches. :) Thanks, > > Kelly > kbyanc@{posi.net,FreeBSD.org} > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- Kelly Yancey - kbyanc@posi.net - Belmont, CA Lead Engineer, Backplane, Inc. http://www.backplane.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 15:20:37 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 1014837B402 for ; Thu, 21 Feb 2002 15:20:24 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020221232023.DYBM1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Thu, 21 Feb 2002 23:20:23 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA69935; Thu, 21 Feb 2002 15:10:23 -0800 (PST) Date: Thu, 21 Feb 2002 15:10:23 -0800 (PST) From: Julian Elischer To: Julian Stacey Cc: Rick M , scsi@freebsd.org Subject: Re: Hi Julian, Can I impose alittle please. In-Reply-To: <200202212232.g1LMWoQ03574@jhs.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Actually I'm going to bounce it to scsi@freebsd.org as I no longer do SCSI and am 6 years out of date. :-) On Thu, 21 Feb 2002, Julian Stacey wrote: > > I guess you'r looking for Julian Elischer of FreeBSD SCSI fame right ? > > He's julian@freebsd.org cc'd > > I'm just Julian Stacey, some guy in Munich who doesnt know you, > isnt a a SCSI guru, & doesnt know why your asking me :-) > you could also try posting to > scsi@freebsd.org > > Good Luck > > Julian > J.Stacey Munich Unix (FreeBSD, Linux etc) Independent Consultant > Free Software with Free Sources: http://bim.bsn.com/~jhs/free/ > Ihr Rauchen = mein allergischer Kopfschmerz ! Schnupftabak probieren ! > > Reference: > > From: Rick M > > Date: Wed, 20 Feb 2002 19:14:25 +0100 > > Message-id: > > Rick M wrote: > > I have a major problem starting to occur accross several of my freebsd > > boxes, releases 4.2 and 4.3, I am out of ideas. > > > > I am running adaptec 2940UW and one 39160, IBM drives. > > > > I keeping getting SCB errors on my net news server during a fast RM. > > Which means I can't expire. > > > > **What is worse my mail server and my webserver started showing the same > > problems.*** > > > > example from webserver: > > Feb 20 10:38:10 avalanche /kernel: (da1:ahc0:0:1:0): SCB 0x17 - timed out > > in Dat > > a-in phase, SEQADDR == 0x76 > > Feb 20 10:38:20 avalanche /kernel: STACK == 0x93, 0x18c, 0x15c, 0x0 > > Feb 20 10:38:20 avalanche /kernel: SXFRCTL0 == 0xa0 > > Feb 20 10:38:20 avalanche /kernel: SCB count = 30 > > Feb 20 10:38:20 avalanche /kernel: QINFIFO entries: 24 3 1 16 26 7 4 0 13 > > 29 2 2 > > 8 18 12 10 25 5 22 11 > > Feb 20 10:38:20 avalanche /kernel: Waiting Queue entries: > > Feb 20 10:38:20 avalanche /kernel: Disconnected Queue entries: > > Feb 20 10:38:20 avalanche /kernel: QOUTFIFO entries: > > Feb 20 10:38:20 avalanche /kernel: Sequencer Free SCB List: 10 1 5 6 14 11 > > 7 9 4 > > 15 8 12 2 0 13 > > Feb 20 10:38:20 avalanche /kernel: Pending list: 11 22 5 25 10 12 18 28 2 > > 29 13 > > 0 4 7 26 16 1 3 24 23 > > Feb 20 10:38:20 avalanche /kernel: Kernel Free SCB list: 15 20 19 17 6 8 > > 14 21 9 > > > > Feb 20 10:38:20 avalanche /kernel: sg[0] - Addr 0xe4c8000 : Length 4096 > > Feb 20 10:38:20 avalanche /kernel: sg[1] - Addr 0xe689000 : Length 4096 > > Feb 20 10:38:20 avalanche /kernel: sg[2] - Addr 0xedca000 : Length 4096 > > Feb 20 10:38:20 avalanche /kernel: sg[3] - Addr 0xe3eb000 : Length 4096 > > Feb 20 10:38:20 avalanche /kernel: sg[4] - Addr 0x94ac000 : Length 4096 > > Feb 20 10:38:20 avalanche /kernel: sg[5] - Addr 0xd40d000 : Length 4096 > > Feb 20 10:38:20 avalanche /kernel: sg[6] - Addr 0xce8e000 : Length 4096 > > Feb 20 10:38:21 avalanche /kernel: sg[8] - Addr 0xcd30000 : Length 4096 > > Feb 20 10:38:21 avalanche /kernel: (da1:ahc0:0:1:0): BDR message in > > message buff > > er > > Feb 20 10:38:21 avalanche /kernel: (da1:ahc0:0:1:0): SCB 0x17 - timed out > > in Dat > > a-in phase, SEQADDR == 0x76 > > Feb 20 10:38:21 avalanche /kernel: STACK == 0x93, 0x18c, 0x15c, 0x0 > > Feb 20 10:38:21 avalanche /kernel: SXFRCTL0 == 0xa0 > > Feb 20 10:38:21 avalanche /kernel: SCB count = 30 > > Feb 20 10:38:21 avalanche /kernel: QINFIFO entries: 24 3 1 16 26 7 4 0 13 > > 29 2 2 > > 8 18 12 10 25 5 22 11 > > Feb 20 10:38:21 avalanche /kernel: Waiting Queue entries: > > Feb 20 10:38:21 avalanche /kernel: Disconnected Queue entries: > > Feb 20 10:38:21 avalanche /kernel: QOUTFIFO entries: > > Feb 20 10:38:21 avalanche /kernel: Sequencer Free SCB List: 10 1 5 6 14 11 > > 7 9 4 > > 15 8 12 2 0 13 > > Feb 20 10:38:21 avalanche /kernel: Pending list: 11 22 5 25 10 12 18 28 2 > > 29 13 > > 0 4 7 26 16 1 3 24 23 > > Feb 20 10:38:21 avalanche /kernel: Kernel Free SCB list: 15 20 19 17 6 8 > > 14 21 9 > > > > Feb 20 10:38:21 avalanche /kernel: sg[0] - Addr 0xe4c8000 : Length 4096 > > Feb 20 10:38:21 avalanche /kernel: sg[1] - Addr 0xe689000 : Length 4096 > > Feb 20 10:38:21 avalanche /kernel: sg[2] - Addr 0xedca000 : Length 4096 > > Feb 20 10:38:22 avalanche /kernel: sg[4] - Addr 0x94ac000 : Length 4096 > > Feb 20 10:38:22 avalanche /kernel: sg[5] - Addr 0xd40d000 : Length 4096 > > Feb 20 10:38:22 avalanche /kernel: sg[6] - Addr 0xce8e000 : Length 4096 > > Feb 20 10:38:22 avalanche /kernel: sg[7] - Addr 0xd80f000 : Length 4096 > > Feb 20 10:38:22 avalanche /kernel: sg[8] - Addr 0xcd30000 : Length 4096 > > Feb 20 10:38:22 avalanche /kernel: (da1:ahc0:0:1:0): no longer in timeout, > > statu > > s = 34b > > Feb 20 10:38:22 avalanche /kernel: ahc0: Issued Channel A Bus Reset. 20 > > SCBs aborted > > > > > > Thanks, > > > > Rick > > > > > > > Julian > J.Stacey Munich Unix (FreeBSD, Linux etc) Independent Consultant > Reduce costs to secure jobs: Use free software: http://bim.bsn.com/~jhs/free/ > Ihr Rauchen = mein allergischer Kopfschmerz ! Schnupftabak probieren ! > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 21:18:48 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.sat.t.u-tokyo.ac.jp (nat.keisu.t.u-tokyo.ac.jp [133.11.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 6AB4137B404 for ; Thu, 21 Feb 2002 21:18:43 -0800 (PST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by mail.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id 1325C2DAC4; Fri, 22 Feb 2002 14:18:42 +0900 (JST) Date: Fri, 22 Feb 2002 14:18:41 +0900 Message-ID: From: Hidetoshi Shimokawa To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: READ_6 patch (Re: RBC support patch) In-Reply-To: <200202211901.g1LJ1nI48461@aslan.scsiguy.com> References: <200202211901.g1LJ1nI48461@aslan.scsiguy.com> User-Agent: Wanderlust/2.4.1 (Stand By Me) REMI/1.14.3 (Matsudai) FLIM/1.13.2 (Kasanui) APEL/10.3 MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At Thu, 21 Feb 2002 12:01:49 -0700, Justin T. Gibbs wrote: > Close. Perform the test inside daerror(). Daerror is supposed to filter > out any errors specific to the da driver prior to calling the generic > error routine, so this is the place to handle this. You should also only > need to do the filtering if the ccb has an error flagged in its ccb > header. This should avoid any unecessary work on transactions that > haven't failed. Lastly, you need to actually requeue the transaction > (xpt_action() followed by a release of the device queue if the transaction > was marked as having frozen the queue). Thanks for the review. The patch is revised. I don't know why xpt_action causes panic. Do you mean xpt_action inside of "if ((ccb->ccb_h.status & CAM_DEV_QFRZN).."? /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html Index: scsi_da.c =================================================================== RCS file: /pub/FreeBSD-CVS/src/sys/cam/scsi/scsi_da.c,v retrieving revision 1.42.2.21 diff -u -r1.42.2.21 scsi_da.c --- scsi_da.c 4 Feb 2002 10:39:57 -0000 1.42.2.21 +++ scsi_da.c 22 Feb 2002 05:16:53 -0000 @@ -1551,14 +1551,68 @@ xpt_release_ccb(done_ccb); } +static void +cmd6to10(struct ccb_scsiio *csio) +{ + struct scsi_rw_6 cmd6; + struct scsi_rw_10 *cmd10; + + bcopy(&csio->cdb_io.cdb_bytes, &cmd6, sizeof(struct scsi_rw_6)); + cmd10 = (struct scsi_rw_10 *) &csio->cdb_io.cdb_bytes; + cmd10->opcode = (cmd6.opcode == READ_6) ? READ_10 : WRITE_10; + cmd10->byte2 = 0; + scsi_ulto4b(scsi_3btoul(cmd6.addr), cmd10->addr); + cmd10->reserved = 0; + scsi_ulto2b(cmd6.length, cmd10->length); + cmd10->control = cmd6.control; + csio->cdb_len = sizeof(*cmd10); +} + static int daerror(union ccb *ccb, u_int32_t cam_flags, u_int32_t sense_flags) { struct da_softc *softc; struct cam_periph *periph; + struct ccb_scsiio *csio; + u_int8_t opcode; periph = xpt_path_periph(ccb->ccb_h.path); softc = (struct da_softc *)periph->softc; + + /* + * XXX + * Work around for broken direct access device + * which doesn't support READ(6)/WRITE(6). + */ + csio = &ccb->csio; + opcode = ((struct scsi_rw_6 *)csio->cdb_io.cdb_bytes)->opcode; + if (((ccb->ccb_h.status & CAM_STATUS_MASK) == CAM_SCSI_STATUS_ERROR) + & (opcode == READ_6 || opcode == WRITE_6)) { + int sense_key, error_code; + int asc, ascq; + scsi_extract_sense(&csio->sense_data, + &error_code, + &sense_key, + &asc, &ascq); + if (sense_key == SSD_KEY_ILLEGAL_REQUEST) { + printf("READ(6)/WRITE(6) failed, " + "minimum_cmd_size is increased to 10.\n"); + softc->minimum_cmd_size = 10; + /* command translation */ + cmd6to10(csio); + /* requeue */ + ccb->ccb_h.status = CAM_REQUEUE_REQ; +#if 0 + xpt_action(ccb); +#endif + if ((ccb->ccb_h.status & CAM_DEV_QFRZN) != 0) + cam_release_devq(ccb->ccb_h.path, + /*relsim_flags*/0, + /*reduction*/0, + /*timeout*/0, + /*getcount_only*/0); + } + } /* * XXX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 21 23:20: 9 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 7FADF37B417 for ; Thu, 21 Feb 2002 23:20:06 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id IAA29140; Fri, 22 Feb 2002 08:20:04 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1M7Iiw52394; Fri, 22 Feb 2002 08:18:44 +0100 (MET) (envelope-from j) Date: Fri, 22 Feb 2002 08:18:44 +0100 From: Joerg Wunsch To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch Message-ID: <20020222081844.D34036@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG References: <200202212212.g1LMCVI52438@aslan.scsiguy.com> <20020221002808.F2337-100000@gerard> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20020221002808.F2337-100000@gerard>; from groudier@free.fr on Thu, Feb 21, 2002 at 12:47:02AM +0100 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Gérard Roudier wrote: > Even if your obviousness is different from mine, at least, we should > not want to send a 6 byte R|W command to a DA devices that did > report capacity >= 1024 MB, for example. Btw., 8 GB is the limit (2^24 blocks). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 22 11:42:49 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id D21F537B402 for ; Fri, 22 Feb 2002 11:42:47 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020222194247.CLIK1147.rwcrmhc52.attbi.com@gateway.posi.net>; Fri, 22 Feb 2002 19:42:47 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1MJgkZ91664; Fri, 22 Feb 2002 11:42:46 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Fri, 22 Feb 2002 11:42:46 -0800 (PST) From: Kelly Yancey To: Joerg Wunsch Cc: =?iso-8859-1?Q?G=E9rard_Roudier?= , Subject: Re: RBC support patch In-Reply-To: <20020222081844.D34036@uriah.heep.sax.de> Message-ID: <20020222113901.G91617-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 22 Feb 2002, Joerg Wunsch wrote: > As G=E9rard Roudier wrote: > > > Even if your obviousness is different from mine, at least, we should > > not want to send a 6 byte R|W command to a DA devices that did > > report capacity >=3D 1024 MB, for example. > > Btw., 8 GB is the limit (2^24 blocks). > > -- > cheers, J"org .-.-. --... ...-- -.. . DL8DTL > No he is correct. READ(6) uses a 21bit LBA; the high 3 bits of the 3rd b= yte are the logical unit number. 2^21 =3D 2097152 sectors; sectors are normall= y 512 bytes so you get 1073741824 (1024M) bytes. Kelly kbyanc@{posi.net,FreeBSD.org} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 22 13:30:13 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id ED68837B402 for ; Fri, 22 Feb 2002 13:30:08 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id WAA14963; Fri, 22 Feb 2002 22:30:04 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1MLNxN68098; Fri, 22 Feb 2002 22:23:59 +0100 (MET) (envelope-from j) Date: Fri, 22 Feb 2002 22:23:59 +0100 From: Joerg Wunsch To: Kelly Yancey Cc: =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG Subject: Re: RBC support patch Message-ID: <20020222222359.A68079@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , Kelly Yancey , =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG References: <20020222081844.D34036@uriah.heep.sax.de> <20020222113901.G91617-100000@gateway.posi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020222113901.G91617-100000@gateway.posi.net>; from kbyanc@posi.net on Fri, Feb 22, 2002 at 11:42:46AM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Kelly Yancey wrote: > No he is correct. READ(6) uses a 21bit LBA; the high 3 bits > of the 3rd byte are the logical unit number. 2^21 = 2097152 > sectors; sectors are normally 512 bytes so you get 1073741824 > (1024M) bytes. Thank you both for correcting me. I only remembered the 3-byte value, but forgot about the prehistoric LUN bits. Should have looked into the standard before. ;-) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message