From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 14 11:07:07 2008 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 314C416A496 for ; Mon, 14 Jan 2008 11:07:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2C82813C4D9 for ; Mon, 14 Jan 2008 11:07:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0EB764i052680 for ; Mon, 14 Jan 2008 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0EB76fJ052676 for freebsd-scsi@FreeBSD.org; Mon, 14 Jan 2008 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Jan 2008 11:07:06 GMT Message-Id: <200801141107.m0EB76fJ052676@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2008 11:07:07 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/40895 scsi wierd kernel / device driver bug o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/60598 scsi wire down of scsi devices conflicts with config o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 o kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceProbeInfo comm o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/93128 scsi [sym] FreeBSD 6.1 BETA 1 has problems with Symbios/LSI o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/99954 scsi [ahc] reading from DVD failes on 6.x (regression) o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks 15 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce o kern/38828 scsi [feature request] DPT PM2012B/90 doesn't work o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs 5 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 14 18:45:33 2008 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 982E616A418; Mon, 14 Jan 2008 18:45:33 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5FE0D13C4CC; Mon, 14 Jan 2008 18:45:33 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0EIjXFt076533; Mon, 14 Jan 2008 18:45:33 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0EIjXoM076529; Mon, 14 Jan 2008 18:45:33 GMT (envelope-from linimon) Date: Mon, 14 Jan 2008 18:45:33 GMT Message-Id: <200801141845.m0EIjXoM076529@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-scsi@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/119668: [cam] [patch] certain errors are too verbose comparing to their importance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2008 18:45:33 -0000 Old Synopsis: [cam] certain errors are too verbose comparing to their importance New Synopsis: [cam] [patch] certain errors are too verbose comparing to their importance Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 14 18:45:14 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=119668 From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 15 16:00:43 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA8C516A420 for ; Tue, 15 Jan 2008 16:00:43 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from abbe.salford.ac.uk (abbe.salford.ac.uk [146.87.0.10]) by mx1.freebsd.org (Postfix) with SMTP id 0C59D13C455 for ; Tue, 15 Jan 2008 16:00:42 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 35674 invoked by uid 98); 15 Jan 2008 15:34:02 +0000 Received: from 146.87.255.121 by abbe.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/5425. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.039977 secs); 15 Jan 2008 15:34:02 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by abbe.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Tue, 15 Jan 2008 15:34:02 +0000 Received: (qmail 39976 invoked by uid 1002); 15 Jan 2008 15:33:59 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Jan 2008 15:33:59 -0000 Date: Tue, 15 Jan 2008 15:33:59 +0000 (GMT) From: "Mark Powell" To: freebsd-scsi@freebsd.org Message-ID: <20080115153046.U39949@rust.salford.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Opening a write-protected tape for writing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2008 16:00:43 -0000 Hi, In 7.0-PRERELEASE, it seems that it is possible to open a write-protected tape for writing. Shouldn't this fail with an error? Cheers. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 6843 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 15 20:24:44 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D81F16A419 for ; Tue, 15 Jan 2008 20:24:44 +0000 (UTC) (envelope-from robin.blanchard@itos.uga.edu) Received: from MAIL.itos.uga.edu (outgoing.itos.uga.edu [128.192.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id 031B613C43E for ; Tue, 15 Jan 2008 20:24:38 +0000 (UTC) (envelope-from robin.blanchard@itos.uga.edu) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 15 Jan 2008 15:12:34 -0500 Message-ID: <1C28E42139C61D4BB4F418A19EAA2E3507B169@MAIL.itos.uga.edu> In-Reply-To: <478D0FB7.8060404@case.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LTO-3 / scsi woes Thread-Index: AchXsJ57G1OCuVc7TGWQC9NKmMUHjAAAaOpA References: <478D04A4.9000103@case.edu> <1C28E42139C61D4BB4F418A19EAA2E3507B168@MAIL.itos.uga.edu> <478D0FB7.8060404@case.edu> From: "Robin Blanchard" To: "Bob Hetzel" Cc: freebsd-scsi@freebsd.org Subject: RE: LTO-3 / scsi woes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2008 20:24:44 -0000 By "bypass" I mean I plugged the LTO drive directly to the controller rather than in-line through the library. I am only using sym0 (the LVD channel). These are the devices in question: at scbus0 target 0 lun 0 (ch0,pass0) at scbus0 target 1 lun 0 (sa0,pass1) Thanks for your help.... > -----Original Message----- > From: Bob Hetzel [mailto:beh@case.edu] > Sent: Tuesday, January 15, 2008 2:56 PM > To: Robin Blanchard > Subject: Re: [Bacula-users] LTO-3 / scsi woes >=20 > Robin, >=20 > The Freebsd log says the controller is operating at Fast-80... that > doesn't sound good. I also noted that it's a dual channel with the > other channel operating SE (single ended which is "high voltage" scsi > as > opposed to LVD or low voltage. >=20 > Also, when you say "bypassed" can you clarify? >=20 > Bob >=20 > Robin Blanchard wrote: > > Bob, > > > > Thanks for the length reply and suggestions. I've swapped terminators > > (I've got a U160 and a U320, both with indicator lights -- both > indicate > > 'green'), as well as cables, cards, and even the drive itself (we > have > > two of the same library, each with a single drive in each). The > > "closest" I've come thus far is to bypass the library/exchanger, and > > connect only the LTO-3 drive; but having to set the speed to 20 MB/s. > > Using an adaptec card, I get absolutely nowhere at all, hence the > > current use of the LSI card (which, yes, is LVD/SE). I just installed > > FBSD (as opposed to RHEL5) to see if I could glean anything else > useful. > > The attached dmesg is FBSD 6.2-STABLE with the LSI (sym) card, and > the > > library/drive both set in the BIOS to defaults/auto. > > > > > > With an adaptec 2940U2W, I get nothing but garbage: > > > > <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> > > (probe0:ahc0:0:0:3): SCB 0xe - timed out > > sg[0] - Addr 0x37d084 : Length 36 > > (probe0:ahc0:0:0:3): Other SCB Timeout > > ahc0: Timedout SCBs already complete. Interrupts may not be > functioning. > > ahc0: Recovery Initiated > >>>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< > > ahc0: Dumping Card State in Data-in phase, at SEQADDR 0xa0 > > Card was paused > > ACCUM =3D 0x40, SINDEX =3D 0xa, DINDEX =3D 0xe4, ARG_2 =3D 0x0 > > HCNT =3D 0x0 SCBPTR =3D 0x0 > > SCSISIGI[0x54]:(BSYI|ATNI|IOI) ERROR[0x0] SCSIBUSL[0x0] > > LASTPHASE[0x40]:(IOI) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) > > SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x93]:(SINGLE_EDGE|WIDEXFER) > > SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0x20]:(DPHASE) > > SSTAT0[0x5]:(DMADONE|SDONE) > > SSTAT1[0x2]:(PHASECHG) SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x8]:(ENSWRAP) > > SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) > > SXFRCTL0[0x88]:(SPIOEN|DFON) DFCNTRL[0x0] > > DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) > > STACK: 0x0 0x167 0x17d 0x84 > > SCB count =3D 20 > > Kernel NEXTQSCB =3D 7 > > Card NEXTQSCB =3D 14 > > QINFIFO entries: 14 > > Waiting Queue entries: > > Disconnected Queue entries: > > QOUTFIFO entries: > > Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 > 19 > > 20 21 22 23 24 25 26 27 28 29 30 31 > > Sequencer SCB Info: > > 0 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x17] SCB_LUN[0x1] > > SCB_TAG[0x1] > > 1 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 2 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 3 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 4 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 5 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 6 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 7 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 8 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 9 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 10 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 11 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 12 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 13 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 14 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 15 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 16 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 17 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 18 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 19 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 20 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 21 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 22 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 23 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 24 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 25 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 26 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 27 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 28 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 29 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 30 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > 31 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) > > SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] > > Pending list: > > 14 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x7] SCB_LUN[0x3] > > 1 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x17] SCB_LUN[0x1] > > Kernel Free SCB list: 15 16 17 18 19 0 2 3 4 5 6 8 9 13 12 11 10 > > Untagged Q(0): 14 > > Untagged Q(1): 1 > > > > > > > >> -----Original Message----- > >> From: Bob Hetzel [mailto:beh@case.edu] > >> Sent: Tuesday, January 15, 2008 2:08 PM > >> To: Robin Blanchard > >> Cc: Allan Black > >> Subject: Re: [Bacula-users] LTO-3 / scsi woes > >> > >> Robin, > >> > >> Just a few additions to what Allan said... termination is not simply > >> one > >> size fits all. On most controllers the internal and external > > connector > >> are considered part of the same bus. You need to always terminate > > both > >> ends of the bus. If you don't use a connector the controller > > generally > >> terminates that "stub" for you. If not, the controller is considered > > to > >> be in the middle of the bus, if memory serves, and therefore you'd > > need > >> to terminate both ends with an actual physical terminator or using > the > >> terminator built into the device at the end if it has one (many > > devices > >> no longer come with that option and I don't think any automatically > >> terminate). > >> > >> In any case, you need to read the manual for whatever controller > > you're > >> using and do what it says to do. You also need to look into the > >> instructions about SCSI target ID's too. If you're using cheap > >> internal > >> connectors that aren't keyed there's also a chance you've got one > >> backward. You also need to make sure your terminator is good for > LVD > >> (Ultra 160) devices. I suspect you're only using external devices. > >> Most external terminators have a light and perhaps it'll have info > on > >> it. Some change the light color depending on what it detects on the > >> bus. If the light isn't lit it may not be working properly or you > may > >> have a goofy termpower setting somewhere. > >> > >> I can't seem to google the LSI controller, are you sure it's LVD? > >> > >> Also there are cable length restrictions of around 25 feet total. > >> Additionally, many times the more devices you use the shorter the > > cable > >> you can use (each device has wiring inside it and with every change > in > >> cabling you add noise). > >> > >> If it's an IBM drive you can download IBM diags and extensively test > > it > >> as well as communications to it. Likewise for HP and probably other > >> drives. > >> > >> You also may need to see if the firmware is current on the > controller > >> as > >> sometimes peripherals are shipped with bugs that get fixed in > software > >> later (blame the marketing guys for pushing production schedules > up). > >> It's also likely there's a firmware update available for the drive > but > >> be careful about doing that when you have communications problems as > >> you > >> could render the drive useless if corrupted firmware gets loaded > into > >> it. > >> > >> Bob > >> > >>> Message: 2 > >>> Date: Tue, 15 Jan 2008 00:10:22 +0000 > >>> From: Allan Black > >>> Subject: Re: [Bacula-users] LTO-3 / scsi woes > >>> To: Robin Blanchard > >>> Cc: uganet@listserv.uga.edu, bacula > >>> > >>> Message-ID: <478BF9EE.2020803@btconnect.com> > >>> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed > >>> > >>> Robin Blanchard wrote: > >>>>> I've been around the block with LSI and with adaptec: tried an > > LSI > >>>>> SYMC101, an adaptec 2940U2W and a 39160. I've removed the > >>>>> library/exchange from the equation, using only the LTO-3 drive > >> (and have > >>>>> actually swapped that drive out for another as well), swapped > > SCSI > >>>>> cables, and terminators, and still am getting scsi errors. Anyone > >> got > >>>>> any tips/ideas here ? > >>> To be honest, this looks like a termination problem (or, at least, > a > >> bus > >>> problem of some sort). However, since you appear to have swapped > out > >> every > >>> piece of hardware, the only thing left seems to be the > configuration > >> .... > >>> Both the external and the internal segments of the SCSI bus need to > >> be > >>> properly terminated. If not, errors will occur on the bus and the > > HBA > >> will > >>> step back the clock speed in an attempt to make the bus work > >> reliably. So > >>> far so good - you are seeing parity errors and the HBA is stepping > >> the > >>> speed back from 160 MB/s to 40 MB/s. > >>> > >>> It looks as if there is either insufficient termination, or too > much > >>> termination, on the bus - too much termination can be as bad as no > >>> termination. > >>> > >>> There should be configuration options in the HBA's BIOS to set > >> termination > >>> of the internal and external segments at the HBA. Usually > > termination > >> of > >>> the external and internal segments are configured independently. > > They > >> can > >>> usually be set to auto (which is usually the default and the > >> manufacturer's > >>> recommended setting), or explicitly on or off. Check you do not > have > >>> termination switched on at the HBA *and* a terminator at the end of > >> the > >>> cable. > >>> > >>> Is the LTO3 drive internal or external, BTW? The internal segment > of > >> the > >>> bus needs to follow the same rules as the external segment, but is > >> usually > >>> more difficult to get right - termination can occur at the HBA, the > >> drive(s) > >>> or the end of the cable. Normally for an Ultra 160 SCSI bus, the > >> internal > >>> segment should have termination switched off (or set to auto) at > the > >> HBA, > >>> the devices on the bus should be unterminated and the ribbon cable > >> should > >>> be terminated. > >>> > >>> Similarly (but less likely), check there is not an option in the > > LTO3 > >> drive > >>> to terminate the bus. If the drive is terminating the bus, *and* > >> there is > >>> a terminator screwed onto the back, this will add up to too much > >>> termination. Like I said, this is unlikely. If anything, if the > > drive > >> can > >>> terminate the bus, it will most probably be automatic. > >>> > >>> If you have a mixture of wide and narrow devices on the bus > >> (particularly > >>> the internal segment) termination can get a bit tricky :-) > >>> > >>> I have never used any of the 3 HBAs you mention at the start of the > >> email, > >>> but I have used a 2940N and a 29160N. A couple of points - the > 2940N > >> did not > >>> (as far as I can remember) have an "auto" setting for bus > > termination > >> at > >>> the HBA; it could only be set to "on" or "off". The 2940UW may be > > the > >> same. > >>> Also, the 29160 BIOS tests the bus segments and reports if it > > detects > >> a > >>> termination problem. The 39160 is, I believe, similar to the 29000 > >> series, > >>> being mainly a dual-channel version. It may tell you of a > > termination > >>> problem if you look carefully at the BIOS output (and try not to > >> blink > >>> at the wrong time in case you miss it :-) > >>> > >>> Depending on how the HBA works, it is possible that a termination > >> error > >>> on one segment will affect both segments. If, for example, you have > >> an > >>> external device attached, but no internal devices, then the HBA > >> should have > >>> termination *on* for the internal segment, and *off* for the > > external > >>> segment. [Or "auto", of course.] > >>> > >>> Allan > >>> From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 16 16:12:57 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F9F316A417 for ; Wed, 16 Jan 2008 16:12:57 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id A237B13C45B for ; Wed, 16 Jan 2008 16:12:56 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m0GGCrZg089769; Wed, 16 Jan 2008 09:12:53 -0700 (MST) (envelope-from scottl@samsco.org) Message-Id: <59016B65-C533-47A4-9E9B-EA2AC8EAA1DF@samsco.org> From: Scott Long To: Mark Powell In-Reply-To: <20080115153046.U39949@rust.salford.ac.uk> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Wed, 16 Jan 2008 09:12:52 -0700 References: <20080115153046.U39949@rust.salford.ac.uk> X-Mailer: Apple Mail (2.915) X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 16 Jan 2008 09:12:53 -0700 (MST) X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: Opening a write-protected tape for writing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2008 16:12:57 -0000 On Jan 15, 2008, at 8:33 AM, Mark Powell wrote: > Hi, > In 7.0-PRERELEASE, it seems that it is possible to open a write- > protected tape for writing. Shouldn't this fail with an error? > Cheers. > Which device node are you opening? Is this a regression from FreeBSD 6? Scott From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 16 16:28:39 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EF1116A418 for ; Wed, 16 Jan 2008 16:28:39 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 17B9913C469 for ; Wed, 16 Jan 2008 16:28:38 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m0GGSQHB090228; Wed, 16 Jan 2008 09:28:27 -0700 (MST) (envelope-from scottl@samsco.org) Message-Id: <24BA641E-E301-4DAB-AB2E-161E47737BA8@samsco.org> From: Scott Long To: Robin Blanchard In-Reply-To: <1C28E42139C61D4BB4F418A19EAA2E3507B169@MAIL.itos.uga.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Wed, 16 Jan 2008 09:28:26 -0700 References: <478D04A4.9000103@case.edu> <1C28E42139C61D4BB4F418A19EAA2E3507B168@MAIL.itos.uga.edu> <478D0FB7.8060404@case.edu> <1C28E42139C61D4BB4F418A19EAA2E3507B169@MAIL.itos.uga.edu> X-Mailer: Apple Mail (2.915) X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 16 Jan 2008 09:28:27 -0700 (MST) X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Bob Hetzel , freebsd-scsi@freebsd.org Subject: Re: LTO-3 / scsi woes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2008 16:28:39 -0000 See my responses inline..... On Jan 15, 2008, at 1:12 PM, Robin Blanchard wrote: > By "bypass" I mean I plugged the LTO drive directly to the controller > rather than in-line through the library. I am only using sym0 (the LVD > channel). > > These are the devices in question: > at scbus0 target 0 lun 0 > (ch0,pass0) > at scbus0 target 1 lun 0 > (sa0,pass1) > I'm trying to reconstruct the conversation here. Are you saying that you've tried LSI, Adaptec, and Symbios controllers, and they've all failed with your drive? > > Thanks for your help.... > >> -----Original Message----- >> From: Bob Hetzel [mailto:beh@case.edu] >> Sent: Tuesday, January 15, 2008 2:56 PM >> To: Robin Blanchard >> Subject: Re: [Bacula-users] LTO-3 / scsi woes >> >> Robin, >> >> The Freebsd log says the controller is operating at Fast-80... that >> doesn't sound good. I also noted that it's a dual channel with the >> other channel operating SE (single ended which is "high voltage" scsi >> as >> opposed to LVD or low voltage. >> SE does not mean "high voltage scsi", HVD does. A bus can operate at either LVD, HVD, or SE. LVD and SE are compatible in the sense that LVD and SE peripherals can interoperate with an LVD or SE controller, with the only caveat being that the presence of any SE devices will bring everything down to SE speeds (20MHz bus). HVD can not interoperate with these, and any attempt to do so will likely cause nothing short of a _fire_. Also, I don't understand your comment about the controller reporting that it's operating in Fast-80 mode. >> Also, when you say "bypassed" can you clarify? >> >> Bob >> >> Robin Blanchard wrote: >>> Bob, >>> >>> Thanks for the length reply and suggestions. I've swapped > terminators >>> (I've got a U160 and a U320, both with indicator lights -- both >> indicate >>> 'green'), as well as cables, cards, and even the drive itself (we >> have >>> two of the same library, each with a single drive in each). The >>> "closest" I've come thus far is to bypass the library/exchanger, and >>> connect only the LTO-3 drive; but having to set the speed to 20 > MB/s. >>> Using an adaptec card, I get absolutely nowhere at all, hence the >>> current use of the LSI card (which, yes, is LVD/SE). I just > installed >>> FBSD (as opposed to RHEL5) to see if I could glean anything else >> useful. >>> The attached dmesg is FBSD 6.2-STABLE with the LSI (sym) card, and >> the >>> library/drive both set in the BIOS to defaults/auto. >>> >>> >>> With an adaptec 2940U2W, I get nothing but garbage: >>> This means that the device responded to a selection for an INQUIRY command (the first command that is issued to each possible on a bus), but then something went wrong to make the driver think that the command didn't progress to completion. It could be something funky with the bus, termination, controller, or driver, but the suggestion in the error message that interrupts are working could well be a hint here. First of all, are there any other devices on the bus that do work? What kind of system is this, and what version of FreeBSD are you using? Since it sounds like you've tried multiple SCSI cards, have you been putting all of them into the same PCI slot, or have you tried different PCI slots? Have you tried any of the published tricks for working around interrupt problems (disabling ACPI, disabling APIC, etc)? Scott From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 16 17:20:24 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A6A816A41A for ; Wed, 16 Jan 2008 17:20:24 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from akis.salford.ac.uk (akis.salford.ac.uk [146.87.0.14]) by mx1.freebsd.org (Postfix) with SMTP id 7073413C4CE for ; Wed, 16 Jan 2008 17:20:23 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 43297 invoked by uid 98); 16 Jan 2008 17:20:21 +0000 Received: from 146.87.255.121 by akis.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/5425. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.045401 secs); 16 Jan 2008 17:20:21 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by akis.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Wed, 16 Jan 2008 17:20:21 +0000 Received: (qmail 50178 invoked by uid 1002); 16 Jan 2008 17:20:19 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Jan 2008 17:20:19 -0000 Date: Wed, 16 Jan 2008 17:20:19 +0000 (GMT) From: "Mark Powell" To: Scott Long In-Reply-To: <59016B65-C533-47A4-9E9B-EA2AC8EAA1DF@samsco.org> Message-ID: <20080116171123.V48963@rust.salford.ac.uk> References: <20080115153046.U39949@rust.salford.ac.uk> <59016B65-C533-47A4-9E9B-EA2AC8EAA1DF@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-scsi@freebsd.org Subject: Re: Opening a write-protected tape for writing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2008 17:20:24 -0000 On Wed, 16 Jan 2008, Scott Long wrote: > On Jan 15, 2008, at 8:33 AM, Mark Powell wrote: >> Hi, >> In 7.0-PRERELEASE, it seems that it is possible to open a write-protected >> tape for writing. Shouldn't this fail with an error? >> Cheers. > > Which device node are you opening? Scott, I was using /dev/esa0. Using star to perform a multi-volume backup and when prompted for tape 6 I mistakenly put in a write protected tape: ----- star: 3296971 blocks + 0 bytes (total of 216070291456 bytes = 211006144.00k). star: Total 16435725 blocks + 0 bytes (total of 1077131673600 bytes = 1051886400.00k). star: Mount volume #6 on '/dev/esa0' and hit star: 0 blocks + 0 bytes (total of 0 bytes = 0.00k). star: Total 16435725 blocks + 0 bytes (total of 1077131673600 bytes = 1051886400.00k). (sa0:ahc0:0:6:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0 (sa0:ahc0:0:6:0): CAM Status: SCSI Status Error (sa0:ahc0:0:6:0): SCSI Status: Check Condition (sa0:ahc0:0:6:0): DATA PROTECT asc:27,0 (sa0:ahc0:0:6:0): Write protected field replaceable unit: 30 (sa0:ahc0:0:6:0): Unretryable error (sa0:ahc0:0:6:0): failed to write terminating filemark(s) star: Mount volume #7 on '/dev/esa0' and hit ----- Star was able to open the tape O_RDWR, but of course only wrote 0 bytes and assumed EOT. This is on an Adaptec 2940U2W and IBM Ultrium LTO2 drive, but I suspect that has no bearing on this error? > Is this a regression from FreeBSD 6? Actually I'm not sure as I've never made that mistake before. I asked Joerg Schilling (star author) about this and he seemed to think it's a scsi driver bug. Cheers. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 6843 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 17 15:23:57 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CF7016A41A; Thu, 17 Jan 2008 15:23:57 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id D09B513C447; Thu, 17 Jan 2008 15:23:56 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 88D17744021; Thu, 17 Jan 2008 17:23:54 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v6auR7+N8nks; Thu, 17 Jan 2008 17:23:54 +0200 (EET) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [88.81.251.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 2E921744002; Thu, 17 Jan 2008 17:23:54 +0200 (EET) Message-ID: <478F7309.4040606@icyb.net.ua> Date: Thu, 17 Jan 2008 17:23:53 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20071116) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: cd(4) as compared to acd(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2008 15:23:57 -0000 It seems that cd driver lacks couple of useful features as compared to acd: 1. device nodes for individual tracks: this might not be so useful for tracks on audio CDs, but it is especially useful for mixed audio/data CDs and multi-track data CDs; 2. automatic detection of track type (audio/data) and then using proper READ command (e.g. READ CD) in strategy, so that read(2) works even for audio CDs (convenient and easy way of doing digital audio extraction); The second one also breaks "API" compatibility between the drivers: if you want to do digital audio extraction, you have to know underlying device type and use different techniques. It seems that these features are not terribly hard to implement (using acd as an example). I am not volunteering at this moment, but this could be added to some "junior hacker tasks" list. -- Andriy Gapon From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 17 16:37:52 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1DA216A419 for ; Thu, 17 Jan 2008 16:37:52 +0000 (UTC) (envelope-from robin.blanchard@itos.uga.edu) Received: from MAIL.itos.uga.edu (outgoing.itos.uga.edu [128.192.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id 1F05B13C474 for ; Thu, 17 Jan 2008 16:37:43 +0000 (UTC) (envelope-from robin.blanchard@itos.uga.edu) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 17 Jan 2008 11:37:40 -0500 Message-ID: <1C28E42139C61D4BB4F418A19EAA2E3507B17A@MAIL.itos.uga.edu> In-Reply-To: <24BA641E-E301-4DAB-AB2E-161E47737BA8@samsco.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LTO-3 / scsi woes Thread-Index: AchYXOGTn1RhAnbOTFSyNzZLbMkcfgAsuXPg References: <478D04A4.9000103@case.edu> <1C28E42139C61D4BB4F418A19EAA2E3507B168@MAIL.itos.uga.edu> <478D0FB7.8060404@case.edu> <1C28E42139C61D4BB4F418A19EAA2E3507B169@MAIL.itos.uga.edu> <24BA641E-E301-4DAB-AB2E-161E47737BA8@samsco.org> From: "Robin Blanchard" To: Cc: support@qualstar.com, bcheek@cambridgecomputer.com, beh@case.edu, Allan.Black@btconnect.com, Juan Machado Subject: RE: LTO-3 / scsi woes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2008 16:37:52 -0000 I've tried adaptec multiple 2940U2W & 39160 (ahc_pci), as well as an LSI U160 (sym), swapped cables, terminators, the LTO-3 drive itself (we have 2 new identical libraries/drives), removed extraneous PCI cards, and have swapped PCI slots. Ultimately I am stuck with SCSI parity errors. Using the LSI card, the devices "work", albeit severely degraded. Initially, this project began on RHEL5 (per this shop's requirements); but I installed RELENG_6 on it, in hopes of gleaning more useful debugging info. I've just installed yet another adaptec 39160 (flashed to latest BIOS), disabled int13h on both channels, and again am getting nowhere. "Best" thus far has been with the LSI with max throughput being about 4475.6 KB/s (see linux dmesg far below). Bacula test ("crippled" LSI): Wrote blk_block=3D4835000, dev_blk_num=3D3000 VolBytes=3D311,915,455,488 rate=3D4475.5 KB/s Wrote blk_block=3D4840000, dev_blk_num=3D8000 VolBytes=3D312,238,015,488 rate=3D4475.6 KB/s Wrote blk_block=3D4845000, dev_blk_num=3D13000 = VolBytes=3D312,560,575,488 rate=3D4475.6 KB/s Wrote blk_block=3D4850000, dev_blk_num=3D2500 VolBytes=3D312,883,135,488 rate=3D4475.6 KB/s Wrote blk_block=3D4855000, dev_blk_num=3D7500 VolBytes=3D313,205,695,488 rate=3D4475.6 KB/s Wrote blk_block=3D4860000, dev_blk_num=3D12500 = VolBytes=3D313,528,255,488 rate=3D4475.7 KB/s ------------ FBSD-6 dmesg (lsi/sym): Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE-200710 #0: Tue Jan 15 11:15:04 EST 2008 root@lewis.itos.uga.edu:/usr/obj/usr/src/sys/RELENG_6 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf27 Stepping =3D 7 =20 Features=3D0xbfebfbff Features2=3D0x4400 Logical CPUs per core: 2 real memory =3D 2146959360 (2047 MB) avail memory =3D 2095808512 (1998 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 29.0 on pci1 pci2: on pcib2 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x3000-0x300f mem 0xfa200000-0xfa20000f,0xfa800000-0xfaffffff irq 48 at device 1.0 on pci2 twe0: [GIANT-LOCKED] twe0: 2 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 pcib3: at device 31.0 on pci1 pci3: on pcib3 sym0: <1010-33> port 0x4000-0x40ff mem 0xfb044000-0xfb0443ff,0xfb040000-0xfb041fff irq 24 at device 1.0 on pci3 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: [GIANT-LOCKED] sym1: <1010-33> port 0x4400-0x44ff mem 0xfb044400-0xfb0447ff,0xfb042000-0xfb043fff irq 25 at device 1.1 on pci3 sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: [GIANT-LOCKED] em0: port 0x4800-0x483f mem 0xfb000000-0xfb01ffff irq 28 at device 2.0 on pci3 em0: Ethernet address: 00:30:48:2a:57:ea em1: port 0x4840-0x487f mem 0xfb020000-0xfb03ffff irq 29 at device 2.1 on pci3 em1: Ethernet address: 00:30:48:2a:57:eb pcib4: at device 3.0 on pci0 pci4: on pcib4 pcib5: at device 29.0 on pci4 pci5: on pcib5 twe1: <3ware Storage Controller. Driver version 1.50.01.002> port 0x5000-0x500f mem 0xfb200000-0xfb20000f,0xfb800000-0xfbffffff irq 96 at device 1.0 on pci5 twe1: [GIANT-LOCKED] twe1: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 pcib6: at device 31.0 on pci4 pci6: on pcib6 ahc0: port 0x6000-0x60ff mem 0xfc000000-0xfc000fff irq 72 at device 1.0 on pci6 ahc0: [GIANT-LOCKED] aic7890/91: Ultra2 Wide Channel A, SCSI Id=3D7, 32/253 SCBs pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pcib7: at device 30.0 on pci0 pci7: on pcib7 pci7: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2060-0x206f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xc9fff,0xca800-0xcafff,0xcb000- 0xcbfff,0xe0000-0xe3fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.200 msec IP Filter: v4.1.13 initialized. Default =3D block all, Logging =3D = enabled Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. acd0: CDROM at ata0-slave UDMA33 twed0: on twe0 twed0: 114472MB (234439600 sectors) twed1: on twe1 twed1: 1907793MB (3907160064 sectors) sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae (probe1:sym0:0:1:1): AutoSense Failed sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae (probe1:sym0:0:1:2): AutoSense Failed sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae (probe1:sym0:0:1:3): AutoSense Failed sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae (probe1:sym0:0:1:4): AutoSense Failed sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae (probe0:sym0:0:1:5): AutoSense Failed sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae (probe0:sym0:0:1:6): AutoSense Failed sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae (probe0:sym0:0:1:7): AutoSense Failed sa0 at sym0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-3 device=20 sa0: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! hwpmc: TSC/1/0x20 P4/18/0xfff cd0 at ata0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device=20 cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present ch0 at sym0 bus 0 target 0 lun 0 ch0: Removable Changer SCSI-2 device=20 ch0: 3.300MB/s transfers ch0: 20 slots, 2 drives, 1 picker, 0 portals Trying to mount root from ufs:/dev/twed0s1a em0: link state changed to UP -------- FBSD dmesg (39160/ahc) ...been dumping card state for hours... Eg: (probe0:ahc0:0:1:2); SCB 0x7 - timed out Sg[0] - Addr 0x2ca484 : Length 36 (probe0:ahc0:0:1:2) : SCB 7: Immediate reset: Flags =3D 0x660 (probe0:ahc0:0:1:2) : no longer in timeout, status =3D 25b Ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Infinite interrupt loop, INTSTAT =3D 60ahc0: Timedout SCBs already complete. Interrupts may not be functioning -------- RHEL5 (LSI/sym) dmesg: sym0: <1010-33> rev 0x1 at pci 0000:05:02.0 irq 23 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: SCSI BUS has been reset. scsi2 : sym-2.2.3 Vendor: QUALSTAR Model: RLS-8204-20 Rev: 006D Type: Medium Changer ANSI SCSI revision: 02 target2:0:0: Beginning Domain Validation target2:0:0: asynchronous target2:0:0: Ending Domain Validation scsi 2:0:0:0: Attached scsi generic sg2 type 8 target2:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31) Vendor: IBM Model: ULTRIUM-TD3 Rev: 73P5 Type: Sequential-Access ANSI SCSI revision: 03 target2:0:1: Beginning Domain Validation target2:0:1: asynchronous target2:0:1: wide asynchronous target2:0:1: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62) sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d target2:0:1: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62) sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d target2:0:1: Domain Validation detected failure, dropping back target2:0:1: control msgout: c. sym0: TARGET 1 has been reset. target2:0:1: Domain Validation detected failure, dropping back target2:0:1: FAST-40 WIDE SCSI 66.0 MB/s DT (30.3 ns, offset 62) sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d target2:0:1: FAST-40 WIDE SCSI 66.0 MB/s DT (30.3 ns, offset 62) target2:0:1: Domain Validation detected failure, dropping back target2:0:1: FAST-20 WIDE SCSI 40.0 MB/s DT (50 ns, offset 62) sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d target2:0:1: FAST-20 WIDE SCSI 40.0 MB/s DT (50 ns, offset 62) target2:0:1: Domain Validation detected failure, dropping back target2:0:1: FAST-20 WIDE SCSI 38.4 MB/s DT (52 ns, offset 62) sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d target2:0:1: FAST-20 WIDE SCSI 38.4 MB/s DT (52 ns, offset 62) target2:0:1: Domain Validation detected failure, dropping back target2:0:1: FAST-20 WIDE SCSI 26.4 MB/s DT (76 ns, offset 62) scsi 2:0:1:0: ABORT operation started. scsi 2:0:1:0: ABORT operation timed-out. scsi 2:0:1:0: DEVICE RESET operation started. scsi 2:0:1:0: DEVICE RESET operation timed-out. scsi 2:0:1:0: BUS RESET operation started. sym0: SCSI BUS reset detected. sym0: SCSI BUS has been reset. scsi 2:0:1:0: BUS RESET operation complete. target2:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31) target2:0:1: FAST-20 WIDE SCSI 26.4 MB/s DT (76 ns, offset 62) scsi 2:0:1:0: ABORT operation started. scsi 2:0:1:0: ABORT operation timed-out. scsi 2:0:1:0: DEVICE RESET operation started. scsi 2:0:1:0: DEVICE RESET operation timed-out. scsi 2:0:1:0: BUS RESET operation started. sym0: SCSI BUS reset detected. sym0: SCSI BUS has been reset. scsi 2:0:1:0: BUS RESET operation complete. scsi 2:0:1:0: HOST RESET operation started. sym0: SCSI BUS has been reset. scsi 2:0:1:0: HOST RESET operation complete. target2:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31) target2:0:1: FAST-20 WIDE SCSI 26.4 MB/s DT (76 ns, offset 62) sym0:1: ERROR (0:48) (5-25-eb) (3e/68/8c) @ (scriptb 2e0:1500000e). sym0: script cmd =3D 88080000 sym0: regdump: da 10 c0 68 47 3e 01 0a 04 05 00 25 80 01 05 00 00 1c 6f 08 08 00 00 00. sym0: SCSI BUS reset detected. sym0: SCSI BUS has been reset. scsi 2:0:1:0: scsi: Device offlined - not ready after error recovery target2:0:1: Domain Validation detected failure, dropping back target2:0:1: FAST-10 WIDE SCSI 17.8 MB/s DT (112 ns, offset 62) sym0: SCSI parity error detected: SCR1=3D1 DBC=3D8c080000 SBCL=3D2d sym0: SCSI BUS reset detected. sym0: SCSI BUS has been reset. target2:0:1: Domain Validation detected failure, dropping back target2:0:1: Domain Validation detected failure, dropping back target2:0:1: Domain Validation detected failure, dropping back target2:0:1: Domain Validation detected failure, dropping back target2:0:1: Domain Validation detected failure, dropping back target2:0:1: Domain Validation Failure, dropping back to Asynchronous target2:0:1: Domain Validation skipping write tests target2:0:1: Ending Domain Validation scsi 2:0:1:0: Attached scsi generic sg3 type 1 ACPI: PCI Interrupt 0000:05:02.1[B] -> GSI 101 (level, low) -> IRQ 24 sym1: <1010-33> rev 0x1 at pci 0000:05:02.1 irq 24 sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: SCSI BUS has been reset. # cat /proc/scsi/sym53c8xx/{2,3} Chip sym53c1010-33, device id 0x20, revision id 0x1 At PCI address 0000:05:02.0, IRQ 23 Min. period factor 9, Wide SCSI BUS, DT capable Max. started commands 448, max. commands per LUN 64 Chip sym53c1010-33, device id 0x20, revision id 0x1 At PCI address 0000:05:02.1, IRQ 24 Min. period factor 9, Wide SCSI BUS, DT capable Max. started commands 448, max. commands per LUN 64 > -----Original Message----- > From: Scott Long [mailto:scottl@samsco.org] > Sent: Wednesday, January 16, 2008 11:28 AM > To: Robin Blanchard > Cc: Bob Hetzel; freebsd-scsi@freebsd.org > Subject: Re: LTO-3 / scsi woes >=20 > See my responses inline..... >=20 >=20 > On Jan 15, 2008, at 1:12 PM, Robin Blanchard wrote: >=20 > > By "bypass" I mean I plugged the LTO drive directly to the controller > > rather than in-line through the library. I am only using sym0 (the > LVD > > channel). > > > > These are the devices in question: > > at scbus0 target 0 lun 0 > > (ch0,pass0) > > at scbus0 target 1 lun 0 > > (sa0,pass1) > > >=20 > I'm trying to reconstruct the conversation here. Are you saying that > you've tried LSI, Adaptec, and Symbios controllers, and they've all > failed with your drive? > From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 17 20:32:43 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9C1D16A469 for ; Thu, 17 Jan 2008 20:32:43 +0000 (UTC) (envelope-from robin.blanchard@itos.uga.edu) Received: from MAIL.itos.uga.edu (outgoing.itos.uga.edu [128.192.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id 3235813C457 for ; Thu, 17 Jan 2008 20:32:34 +0000 (UTC) (envelope-from robin.blanchard@itos.uga.edu) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 17 Jan 2008 15:19:41 -0500 Message-ID: <1C28E42139C61D4BB4F418A19EAA2E3507B18A@MAIL.itos.uga.edu> In-Reply-To: <1C28E42139C61D4BB4F418A19EAA2E3507B17A@MAIL.itos.uga.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LTO-3 / scsi woes Thread-Index: AchYXOGTn1RhAnbOTFSyNzZLbMkcfgAsuXPgAA1ZC/A= References: <478D04A4.9000103@case.edu><1C28E42139C61D4BB4F418A19EAA2E3507B168@MAIL.itos.uga.edu><478D0FB7.8060404@case.edu><1C28E42139C61D4BB4F418A19EAA2E3507B169@MAIL.itos.uga.edu><24BA641E-E301-4DAB-AB2E-161E47737BA8@samsco.org> <1C28E42139C61D4BB4F418A19EAA2E3507B17A@MAIL.itos.uga.edu> From: "Robin Blanchard" To: Cc: beh@case.edu, Allan.Black@btconnect.com Subject: RE: LTO-3 / scsi woes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2008 20:32:43 -0000 Here's a linux dmesg with the below adaptec suggestions applied. Same server. Still questionable, no ? scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7899: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs scsi 2:0:0:0: Medium Changer QUALSTAR RLS-8204-20 006D PQ: 0 ANSI: 2 target2:0:0: Beginning Domain Validation target2:0:0: Ending Domain Validation scsi 2:0:1:0: Sequential-Access IBM ULTRIUM-TD3 73P5 PQ: 0 ANSI: 3 target2:0:1: Beginning Domain Validation target2:0:1: FAST-40 SCSI 40.0 MB/s ST (25 ns, offset 127) target2:0:1: Domain Validation detected failure, dropping back target2:0:1: FAST-40 SCSI 33.0 MB/s ST (30.3 ns, offset 127) target2:0:1: Domain Validation detected failure, dropping back target2:0:1: FAST-20 SCSI 20.0 MB/s ST (50 ns, offset 127) target2:0:1: Domain Validation skipping write tests target2:0:1: Ending Domain Validation scsi_scan_2 used greatest stack depth: 2644 bytes left scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7899: Ultra160 Wide Channel B, SCSI Id=3D7, 32/253 SCBs adaptec bios mods: domain validation - disabled initiate wide negotaion - no (both library & drive) enable disconnection - no (both library & drive) send start unit command - no (both library & drive) RELENG_6 (with or without these mods) stalls during boot with spurious scsi errors >=20 > I've tried adaptec multiple 2940U2W & 39160 (ahc_pci), as well as an > LSI > U160 (sym), swapped cables, terminators, the LTO-3 drive itself (we > have > 2 new identical libraries/drives), removed extraneous PCI cards, and > have swapped PCI slots. Ultimately I am stuck with SCSI parity errors. > Using the LSI card, the devices "work", albeit severely degraded. > Initially, this project began on RHEL5 (per this shop's requirements); > but I installed RELENG_6 on it, in hopes of gleaning more useful > debugging info. >=20 > I've just installed yet another adaptec 39160 (flashed to latest BIOS), > disabled int13h on both channels, and again am getting nowhere. "Best" > thus far has been with the LSI with max throughput being about 4475.6 > KB/s (see linux dmesg far below). >=20 > Bacula test ("crippled" LSI): >=20 > Wrote blk_block=3D4835000, dev_blk_num=3D3000 = VolBytes=3D311,915,455,488 > rate=3D4475.5 KB/s > Wrote blk_block=3D4840000, dev_blk_num=3D8000 = VolBytes=3D312,238,015,488 > rate=3D4475.6 KB/s > Wrote blk_block=3D4845000, dev_blk_num=3D13000 = VolBytes=3D312,560,575,488 > rate=3D4475.6 KB/s > Wrote blk_block=3D4850000, dev_blk_num=3D2500 = VolBytes=3D312,883,135,488 > rate=3D4475.6 KB/s > Wrote blk_block=3D4855000, dev_blk_num=3D7500 = VolBytes=3D313,205,695,488 > rate=3D4475.6 KB/s > Wrote blk_block=3D4860000, dev_blk_num=3D12500 = VolBytes=3D313,528,255,488 > rate=3D4475.7 KB/s >=20 > ------------ >=20 > FBSD-6 dmesg (lsi/sym): >=20 > Copyright (c) 1992-2007 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 6.2-STABLE-200710 #0: Tue Jan 15 11:15:04 EST 2008 > root@lewis.itos.uga.edu:/usr/obj/usr/src/sys/RELENG_6 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf27 Stepping =3D 7 >=20 > Features=3D0xbfebfbff E > ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=3D0x4400 > Logical CPUs per core: 2 > real memory =3D 2146959360 (2047 MB) > avail memory =3D 2095808512 (1998 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > ioapic2 irqs 48-71 on motherboard > ioapic3 irqs 72-95 on motherboard > ioapic4 irqs 96-119 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pci0: at device 0.1 (no driver attached) > pcib1: at device 2.0 on pci0 > pci1: on pcib1 > pcib2: at device 29.0 on pci1 > pci2: on pcib2 > twe0: <3ware Storage Controller. Driver version 1.50.01.002> port > 0x3000-0x300f mem 0xfa200000-0xfa20000f,0xfa800000-0xfaffffff irq 48 at > device 1.0 on pci2 > twe0: [GIANT-LOCKED] > twe0: 2 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > pcib3: at device 31.0 on pci1 > pci3: on pcib3 > sym0: <1010-33> port 0x4000-0x40ff mem > 0xfb044000-0xfb0443ff,0xfb040000-0xfb041fff irq 24 at device 1.0 on > pci3 > sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym0: handling phase mismatch from SCRIPTS. > sym0: [GIANT-LOCKED] > sym1: <1010-33> port 0x4400-0x44ff mem > 0xfb044400-0xfb0447ff,0xfb042000-0xfb043fff irq 25 at device 1.1 on > pci3 > sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking > sym1: open drain IRQ line driver, using on-chip SRAM > sym1: using LOAD/STORE-based firmware. > sym1: handling phase mismatch from SCRIPTS. > sym1: [GIANT-LOCKED] > em0: port > 0x4800-0x483f mem 0xfb000000-0xfb01ffff irq 28 at device 2.0 on pci3 > em0: Ethernet address: 00:30:48:2a:57:ea > em1: port > 0x4840-0x487f mem 0xfb020000-0xfb03ffff irq 29 at device 2.1 on pci3 > em1: Ethernet address: 00:30:48:2a:57:eb > pcib4: at device 3.0 on pci0 > pci4: on pcib4 > pcib5: at device 29.0 on pci4 > pci5: on pcib5 > twe1: <3ware Storage Controller. Driver version 1.50.01.002> port > 0x5000-0x500f mem 0xfb200000-0xfb20000f,0xfb800000-0xfbffffff irq 96 at > device 1.0 on pci5 > twe1: [GIANT-LOCKED] > twe1: 12 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > pcib6: at device 31.0 on pci4 > pci6: on pcib6 > ahc0: port 0x6000-0x60ff mem > 0xfc000000-0xfc000fff irq 72 at device 1.0 on pci6 > ahc0: [GIANT-LOCKED] > aic7890/91: Ultra2 Wide Channel A, SCSI Id=3D7, 32/253 SCBs > pci0: at device 29.0 (no driver attached) > pci0: at device 29.1 (no driver attached) > pci0: at device 29.2 (no driver attached) > pcib7: at device 30.0 on pci0 > pci7: on pcib7 > pci7: at device 1.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2060-0x206f at device 31.1 on > pci0 > ata0: on atapci0 > ata1: on atapci0 > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0: port 0x378-0x37f,0x778-0x77f irq 7 > drq > 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > orm0: at iomem > 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xc9fff,0xca800- > 0xcafff,0xcb000- > 0xcbfff,0xe0000-0xe3fff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > Timecounters tick every 1.200 msec > IP Filter: v4.1.13 initialized. Default =3D block all, Logging =3D enabled > Waiting 2 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. > acd0: CDROM at ata0-slave UDMA33 > twed0: on twe0 > twed0: 114472MB (234439600 sectors) > twed1: on twe1 > twed1: 1907793MB (3907160064 sectors) > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > (probe1:sym0:0:1:1): AutoSense Failed > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > (probe1:sym0:0:1:2): AutoSense Failed > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > (probe1:sym0:0:1:3): AutoSense Failed > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > (probe1:sym0:0:1:4): AutoSense Failed > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > (probe0:sym0:0:1:5): AutoSense Failed > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > (probe0:sym0:0:1:6): AutoSense Failed > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D1500000e SBCL=3Dae > (probe0:sym0:0:1:7): AutoSense Failed > sa0 at sym0 bus 0 target 1 lun 0 > sa0: Removable Sequential Access SCSI-3 device > sa0: 160.000MB/s transfers (80.000MHz, offset 62, 16bit) > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > hwpmc: TSC/1/0x20 > P4/18/0xfff > cd0 at ata0 bus 0 target 1 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 33.000MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not present > ch0 at sym0 bus 0 target 0 lun 0 > ch0: Removable Changer SCSI-2 device > ch0: 3.300MB/s transfers > ch0: 20 slots, 2 drives, 1 picker, 0 portals > Trying to mount root from ufs:/dev/twed0s1a > em0: link state changed to UP >=20 > -------- >=20 >=20 > FBSD dmesg (39160/ahc) >=20 > ...been dumping card state for hours... >=20 > Eg: >=20 > (probe0:ahc0:0:1:2); SCB 0x7 - timed out > Sg[0] - Addr 0x2ca484 : Length 36 > (probe0:ahc0:0:1:2) : SCB 7: Immediate reset: Flags =3D 0x660 > (probe0:ahc0:0:1:2) : no longer in timeout, status =3D 25b > Ahc0: Issued Channel A Bus Reset. 2 SCBs aborted > Infinite interrupt loop, INTSTAT =3D 60ahc0: Timedout SCBs already > complete. Interrupts may not be functioning >=20 > -------- >=20 > RHEL5 (LSI/sym) dmesg: >=20 > sym0: <1010-33> rev 0x1 at pci 0000:05:02.0 irq 23 > sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym0: handling phase mismatch from SCRIPTS. > sym0: SCSI BUS has been reset. > scsi2 : sym-2.2.3 > Vendor: QUALSTAR Model: RLS-8204-20 Rev: 006D > Type: Medium Changer ANSI SCSI revision: 02 > target2:0:0: Beginning Domain Validation > target2:0:0: asynchronous > target2:0:0: Ending Domain Validation > scsi 2:0:0:0: Attached scsi generic sg2 type 8 > target2:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31) > Vendor: IBM Model: ULTRIUM-TD3 Rev: 73P5 > Type: Sequential-Access ANSI SCSI revision: 03 > target2:0:1: Beginning Domain Validation > target2:0:1: asynchronous > target2:0:1: wide asynchronous > target2:0:1: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62) > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > target2:0:1: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62) > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000002 SBCL=3Dae > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: control msgout: c. > sym0: TARGET 1 has been reset. > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: FAST-40 WIDE SCSI 66.0 MB/s DT (30.3 ns, offset 62) > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > target2:0:1: FAST-40 WIDE SCSI 66.0 MB/s DT (30.3 ns, offset 62) > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: FAST-20 WIDE SCSI 40.0 MB/s DT (50 ns, offset 62) > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > target2:0:1: FAST-20 WIDE SCSI 40.0 MB/s DT (50 ns, offset 62) > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: FAST-20 WIDE SCSI 38.4 MB/s DT (52 ns, offset 62) > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D15000000 SBCL=3D2d > target2:0:1: FAST-20 WIDE SCSI 38.4 MB/s DT (52 ns, offset 62) > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: FAST-20 WIDE SCSI 26.4 MB/s DT (76 ns, offset 62) scsi > 2:0:1:0: ABORT operation started. > scsi 2:0:1:0: ABORT operation timed-out. > scsi 2:0:1:0: DEVICE RESET operation started. > scsi 2:0:1:0: DEVICE RESET operation timed-out. > scsi 2:0:1:0: BUS RESET operation started. > sym0: SCSI BUS reset detected. > sym0: SCSI BUS has been reset. > scsi 2:0:1:0: BUS RESET operation complete. > target2:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31) > target2:0:1: FAST-20 WIDE SCSI 26.4 MB/s DT (76 ns, offset 62) scsi > 2:0:1:0: ABORT operation started. > scsi 2:0:1:0: ABORT operation timed-out. > scsi 2:0:1:0: DEVICE RESET operation started. > scsi 2:0:1:0: DEVICE RESET operation timed-out. > scsi 2:0:1:0: BUS RESET operation started. > sym0: SCSI BUS reset detected. > sym0: SCSI BUS has been reset. > scsi 2:0:1:0: BUS RESET operation complete. > scsi 2:0:1:0: HOST RESET operation started. > sym0: SCSI BUS has been reset. > scsi 2:0:1:0: HOST RESET operation complete. > target2:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31) > target2:0:1: FAST-20 WIDE SCSI 26.4 MB/s DT (76 ns, offset 62) > sym0:1: ERROR (0:48) (5-25-eb) (3e/68/8c) @ (scriptb 2e0:1500000e). > sym0: script cmd =3D 88080000 > sym0: regdump: da 10 c0 68 47 3e 01 0a 04 05 00 25 80 01 05 00 00 1c 6f > 08 08 00 00 00. > sym0: SCSI BUS reset detected. > sym0: SCSI BUS has been reset. > scsi 2:0:1:0: scsi: Device offlined - not ready after error recovery > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: FAST-10 WIDE SCSI 17.8 MB/s DT (112 ns, offset 62) > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D8c080000 SBCL=3D2d > sym0: SCSI BUS reset detected. > sym0: SCSI BUS has been reset. > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: Domain Validation detected failure, dropping back > target2:0:1: Domain Validation Failure, dropping back to Asynchronous > target2:0:1: Domain Validation skipping write tests > target2:0:1: Ending Domain Validation > scsi 2:0:1:0: Attached scsi generic sg3 type 1 > ACPI: PCI Interrupt 0000:05:02.1[B] -> GSI 101 (level, low) -> IRQ 24 > sym1: <1010-33> rev 0x1 at pci 0000:05:02.1 irq 24 > sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking > sym1: open drain IRQ line driver, using on-chip SRAM > sym1: using LOAD/STORE-based firmware. > sym1: handling phase mismatch from SCRIPTS. > sym1: SCSI BUS has been reset. >=20 > # cat /proc/scsi/sym53c8xx/{2,3} > Chip sym53c1010-33, device id 0x20, revision id 0x1 At PCI address > 0000:05:02.0, IRQ 23 Min. period factor 9, Wide SCSI BUS, DT capable > Max. started commands 448, max. commands per LUN 64 Chip sym53c1010-33, > device id 0x20, revision id 0x1 At PCI address 0000:05:02.1, IRQ 24 > Min. > period factor 9, Wide SCSI BUS, DT capable Max. started commands 448, > max. commands per LUN 64 From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 18 06:25:59 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC76816A418 for ; Fri, 18 Jan 2008 06:25:59 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4C41D13C461 for ; Fri, 18 Jan 2008 06:25:59 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id C170E11443; Fri, 18 Jan 2008 17:07:25 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from anzac.hos (132.169.233.220.exetel.com.au [220.233.169.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id B4CA711437; Fri, 18 Jan 2008 17:07:21 +1100 (EST) Message-ID: <47904219.5020001@modulus.org> Date: Fri, 18 Jan 2008 17:07:21 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.0 (X11/20070426) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: iSCSI tests in 7.0-RC1 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2008 06:25:59 -0000 Hi! I have been testing iSCSI initiator using two 7.0-RC1 machines. Machines are quad-core Xeons connected back to back via gigabit. The target is running the same OS with the iscsi-target port talking directly to a local device partition on disk. While it seems to work well initially (I can format, fsck, and mount a disk) after I start copying files in and out it seems to lock up regularly for about 15-20 seconds a time. After it unblocks it continues as if nothing happened until 5-10 seconds later it happens again (and again). Is this a known problem and is there any workaround? - Andrew From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 18 08:01:25 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 703F616A468 for ; Fri, 18 Jan 2008 08:01:25 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 09B2713C45B for ; Fri, 18 Jan 2008 08:01:24 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 4D0B011441; Fri, 18 Jan 2008 19:01:23 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from anzac.hos (132.169.233.220.exetel.com.au [220.233.169.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 31E9311437 for ; Fri, 18 Jan 2008 19:01:15 +1100 (EST) Message-ID: <47905CCA.3050208@modulus.org> Date: Fri, 18 Jan 2008 19:01:14 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.0 (X11/20070426) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: iSCSI tests in 7.0-RC1 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2008 08:01:25 -0000 Danny Braniss wrote: > if you are testing the initiator with the target from ports, then > it does not work if they are both on the same host. Thanks. I am using seperate (but identical) machines. Also, geom_gate works perfectly (well, as well as it normally works, which is not great but serviceable). I was hoping to replace geom_gate with iSCSI. - Andrew From owner-freebsd-scsi@FreeBSD.ORG Sat Jan 19 21:39:13 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22A2616A41A for ; Sat, 19 Jan 2008 21:39:13 +0000 (UTC) (envelope-from freebsd@wcubed.net) Received: from mail.datausa.com (mail.datausa.com [216.150.220.220]) by mx1.freebsd.org (Postfix) with SMTP id D9F4613C4CC for ; Sat, 19 Jan 2008 21:39:12 +0000 (UTC) (envelope-from freebsd@wcubed.net) Received: (qmail 59931 invoked by uid 89); 19 Jan 2008 14:12:29 -0700 Received: from unknown (HELO webmail.wcubed.net) (freebsd@wcubed.net@216.150.220.219) by mail.datausa.com with SMTP; 19 Jan 2008 14:12:29 -0700 Received: from 67.176.75.179 (SquirrelMail authenticated user freebsd@wcubed.net) by webmail.wcubed.net with HTTP; Sat, 19 Jan 2008 14:12:29 -0700 (MST) Message-ID: <59414.67.176.75.179.1200777149.squirrel@webmail.wcubed.net> Date: Sat, 19 Jan 2008 14:12:29 -0700 (MST) From: "Brad Waite" To: freebsd-scsi@freebsd.org User-Agent: SquirrelMail/1.4.10a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: sdparm dumping core X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2008 21:39:13 -0000 Hey guys, Is there any known reason why sdparm would dump core on my 6.2-STABLE install? I'm using an Intel SRCMRU 0-channel RAID in conjunction with an on-board Adaptec AIC-7902 controller. Thanks, Brad Waite Below are some pertinent DMESGes: FreeBSD 6.2-STABLE #0: Sun Jul 15 08:40:35 MDT 2007 CPU: Intel(R) XEON(TM) CPU 2.00GHz (1994.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff Logical CPUs per core: 2 real memory = 1073676288 (1023 MB) avail memory = 1041489920 (993 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs iir0: mem 0xfa000000-0xfbffffff irq 48 at device 8.0 on pci4 iir0: [GIANT-LOCKED] ses0 at iir0 bus 1 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device da0 at iir0 bus 2 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 139941MB (286599600 512 byte sectors: 255H 63S/T 17840C) da1 at iir0 bus 2 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Tagged Queueing Enabled da1: 69962MB (143283735 512 byte sectors: 255H 63S/T 8919C)