From owner-freebsd-scsi Sun Mar 11 19:25:26 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cs4.cs.ait.ac.th (cs4.cs.ait.ac.th [192.41.170.16]) by hub.freebsd.org (Postfix) with ESMTP id 53A0937B718 for ; Sun, 11 Mar 2001 19:25:20 -0800 (PST) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5]) by cs4.cs.ait.ac.th (8.9.3/8.9.3) with ESMTP id KAA01720 for ; Mon, 12 Mar 2001 10:25:03 +0700 (GMT+0700) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.8.5/8.8.5) id KAA09448; Mon, 12 Mar 2001 10:25:10 +0700 (ICT) Date: Mon, 12 Mar 2001 10:25:10 +0700 (ICT) Message-Id: <200103120325.KAA09448@banyan.cs.ait.ac.th> X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f From: Olivier Nicole Cc: freebsd-scsi@FreeBSD.ORG Subject: SCSI speed with SLR100 tape drive Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I finally got that SLR100 tape drive I wanted. It si supposed to support SCSI 160, but anyway the machine I have only supports 80Mb. The problem is the following: - at boot time, going to the Symbios bios, the tape is given at maximum speed, 80 Mb - once FreeBSD is started, it only supports half the speed: sa0 at sym1 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) Any idea on the reason why? Eventually, I had to modify /usr/src/sys/cam/scsi/scsi_sa.c to remove the leading blank from the model name in the quirk table. Best regards, Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 11 20:25:44 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DC7EC37B719 for ; Sun, 11 Mar 2001 20:25:41 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id UAA32765; Sun, 11 Mar 2001 20:25:27 -0800 Date: Sun, 11 Mar 2001 20:25:24 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Olivier Nicole Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI speed with SLR100 tape drive In-Reply-To: <200103120325.KAA09448@banyan.cs.ait.ac.th> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Mar 2001, Olivier Nicole wrote: > > Hello, > > I finally got that SLR100 tape drive I wanted. It si supposed to > support SCSI 160, but anyway the machine I have only supports 80Mb. > > The problem is the following: > > - at boot time, going to the Symbios bios, the tape is given at > maximum speed, 80 Mb > > - once FreeBSD is started, it only supports half the speed: > sa0 at sym1 bus 0 target 2 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > > Any idea on the reason why? It's not 'half the speed'. Please go read some SCSI FAQs somewhere. > > Eventually, I had to modify /usr/src/sys/cam/scsi/scsi_sa.c to remove > the leading blank from the model name in the quirk table. > > Best regards, > > Olivier > > 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 Sun Mar 11 20:45:54 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id 3AA1537B718 for ; Sun, 11 Mar 2001 20:45:47 -0800 (PST) (envelope-from gemorga2@vt.edu) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id f2C4jgu506429; Sun, 11 Mar 2001 23:45:42 -0500 (EST) Received: from enigma ([198.82.102.76]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0GA200E8BIK4UA@gkar.cc.vt.edu>; Sun, 11 Mar 2001 23:45:40 -0500 (EST) Date: Sun, 11 Mar 2001 23:45:40 -0500 From: George Morgan Subject: Re: SCSI speed with SLR100 tape drive In-reply-to: To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Message-id: <3AAC0E24.30330.73F53E@localhost> MIME-version: 1.0 X-Mailer: Pegasus Mail for Win32 (v3.12c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <200103120325.KAA09448@banyan.cs.ait.ac.th> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm, according to the Tandberg website, the SLR100 supports up to Ultra2-Wide SCSI which from what I understand, the Ultra2 narrow bus supports 40 MB/sec max transfer rate and the Ultra2 wide bus supports 80 MB/sec max transfer rate. The probe message suggests that the bus is running at 20 MHz with 16 bits per transfer (wide SCSI) which should mean an effective data rate of 40 MB/sec as listed in the message. To achieve the manufacturer specified Ultra2 performance the bus would have to use a 40 MHz clock rate, unless data is transferred on the rising and falling edges of the clock. According to what I was able to find on the web about SCSI specifications, transfers on the rising and falling edges of the clock are not used until you get to Ultra3/Ultra160 or Ultra320 which this drive does not appear to support. Of course I could be totally wrong since I am not a SCSI expert. Please clarify or provide a URL to an explanation that fits your claims. Thanks. > On Mon, 12 Mar 2001, Olivier Nicole wrote: > > > > > Hello, > > > > I finally got that SLR100 tape drive I wanted. It si supposed to > > support SCSI 160, but anyway the machine I have only supports 80Mb. > > > > The problem is the following: > > > > - at boot time, going to the Symbios bios, the tape is given at > > maximum speed, 80 Mb > > > > - once FreeBSD is started, it only supports half the speed: > > sa0 at sym1 bus 0 target 2 lun 0 > > sa0: Removable Sequential Access SCSI-2 > > device sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > > > > Any idea on the reason why? > > It's not 'half the speed'. Please go read some SCSI FAQs somewhere. > > > > > Eventually, I had to modify /usr/src/sys/cam/scsi/scsi_sa.c to > > remove the leading blank from the model name in the quirk table. > > > > > > Best regards, > > > > Olivier > > > > 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 George Morgan Virginia Tech Electrical Engineering Class of 2000 (Graduating May 2001 as a Co-op) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 11 21:18:32 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cs4.cs.ait.ac.th (cs4.cs.ait.ac.th [192.41.170.16]) by hub.freebsd.org (Postfix) with ESMTP id 7B6CB37B719 for ; Sun, 11 Mar 2001 21:18:28 -0800 (PST) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5]) by cs4.cs.ait.ac.th (8.9.3/8.9.3) with ESMTP id MAA03364; Mon, 12 Mar 2001 12:18:11 +0700 (GMT+0700) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.8.5/8.8.5) id MAA09550; Mon, 12 Mar 2001 12:18:17 +0700 (ICT) Date: Mon, 12 Mar 2001 12:18:17 +0700 (ICT) Message-Id: <200103120518.MAA09550@banyan.cs.ait.ac.th> X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f From: Olivier Nicole To: gemorga2@vt.edu Cc: mjacob@feral.com, freebsd-scsi@FreeBSD.ORG In-reply-to: <3AAC0E24.30330.73F53E@localhost> (message from George Morgan on Sun, 11 Mar 2001 23:45:40 -0500) Subject: Re: SCSI speed with SLR100 tape drive References: <200103120325.KAA09448@banyan.cs.ait.ac.th> <3AAC0E24.30330.73F53E@localhost> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hmm, according to the Tandberg website, the SLR100 supports up to >Ultra2-Wide SCSI which from what I understand, the Ultra2 narrow bus OK, my mistake. I thought I read somewhere it supported Ultra 160. But anyway, why Symbios bios (at PC boot) says 80MB/s while FreeBSD only says 40MB/s? From other discussions, I understand that acheiving a good speed on the SCSI interface is critical to keep the drive streaming (transfer to the tape is about 40 Mbit/s). Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 12: 2:58 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by hub.freebsd.org (Postfix) with ESMTP id 6294737B718 for ; Mon, 12 Mar 2001 12:02:55 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from nas1-233.cgy.club-internet.fr (nas1-233.cgy.club-internet.fr [195.36.197.233]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA28540; Mon, 12 Mar 2001 21:02:39 +0100 (MET) Date: Mon, 12 Mar 2001 18:52:08 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Olivier Nicole Cc: gemorga2@vt.edu, mjacob@feral.com, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI speed with SLR100 tape drive In-Reply-To: <200103120518.MAA09550@banyan.cs.ait.ac.th> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Mar 2001, Olivier Nicole wrote: > >Hmm, according to the Tandberg website, the SLR100 supports up to=20 > >Ultra2-Wide SCSI which from what I understand, the Ultra2 narrow bus=20 >=20 > OK, my mistake. I thought I read somewhere it supported Ultra 160. >=20 > But anyway, why Symbios bios (at PC boot) says 80MB/s while FreeBSD > only says 40MB/s? FreeBSD says if the BUS is operating in LVD mode or in SE (single ended) mode but the Symbios BIOS doesn't. Could you please, post _all_ the messages printed out by the sym driver? Thanks. This information is very important since if the BUS is operating in SE mode, then 40 MB/s is the expected maximum throughput for Wide 16 SCSI devices. > >From other discussions, I understand that acheiving a good speed on > the SCSI interface is critical to keep the drive streaming (transfer > to the tape is about 40 Mbit/s). Some tape drives require hudge data chunks in order to keep streaming. May-be 40 MB/s burst is already enough to feed the tape fast enough to allow it to stream data. G=E9rard.=20 > Olivier >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 12:34:10 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.comm2000.it (mindseal.comm2000.it [194.133.0.6]) by hub.freebsd.org (Postfix) with ESMTP id 3F50737B718 for ; Mon, 12 Mar 2001 12:34:06 -0800 (PST) (envelope-from m.lusetti@datacode.it) Received: from purtroppo.local.lan ([212.97.62.126]) by relay.comm2000.it (8.11.2/MFAGMM-19990726) with ESMTP id f2CKY4H27107 for ; Mon, 12 Mar 2001 21:34:04 +0100 X-SMTP-Peer: [212.97.62.126] Received: from massimo (massimo.local.lan [192.168.1.13]) by purtroppo.local.lan (8.11.1/8.11.1) with SMTP id f2CKWaF03797 for ; Mon, 12 Mar 2001 21:32:36 +0100 (CET) (envelope-from m.lusetti@datacode.it) Message-ID: <006b01c0ab33$99842530$0d01a8c0@local.lan> From: "Massimo Lusetti" To: Subject: AIC-7892 & Ultra160 problems Date: Mon, 12 Mar 2001 21:32:47 +0100 Organization: DATACODE s.r.l. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Firt of all Hi everyone cause this is my first message to this list, ok i can go on now... I got a new fresh IBM Netfinity x220 series machine which has a AIC-7892 SCSI controller integrated onboard, that my problems begin. I got this message and mysqld ending with signal 11 when i stress the machine: > (da1:ahc0:0:5:0): SCB 0x47 - timed out while idle, SEQADDR == 0x5 > STACK == 0x1, 0x174, 0x15e, 0x174 > SXFRCTL0 == 0x80 > SCB count = 255 > QINFIFO entries: > Waiting Queue entries: > Disconnected Queue entries: 22:161 12:71 > QOUTFIFO entries: > Sequencer Free SCB List: 21 6 28 20 9 26 15 11 2 27 8 17 23 14 30 3 5 4 31 1 19 0 13 7 24 25 10 18 16 29 > Pending list: 161 71 > Kernel Free SCB list: 208 132 6 19 81 106 43 22 55 253 214 203 7 59 116 110 90 56 79 58 77 169 167 88 50 105 23 147 225 32 27 235 74 17 168 82 46 2 111 4 127 233 61 60 47 117 45 156 57 69 5 38 101 151 135 37 146 102 103 97 96 51 121 211 33 124 11 148 85 130 9 49 99 29 28 94 112 118 158 70 113 64 134 86 133 107 125 76 78 35 84 14 129 152 145 232 191 36 175 44 165 62 131 115 91 136 149 48 100 34 93 13 123 104 229 26 119 197 128 30 109 21 196 230 240 98 234 10 80 251 92 52 150 254 205 18 68 83 40 242 241 247 42 204 199 223 16 248 224 162 180 3 202 153 236 238 239 221 226 227 184 228 176 212 207 181 41 20 219 220 174 190 192 39 166 252 213 154 155 164 185 186 15 189 171 188 183 144 8 217 1 24 54 66 195 179 108 231 157 198 67 222 246 216 172 210 160 182 89 209 250 245 218 31 73 244 12 126 177 187 200 237 122 194 63 201 163 114 249 53 75 170 87 193 173 72 215 178 243 95 25 65 206 159 140 141 138 142 143 120 139 137 > sg[0] - Addr 0xc55b800 : Length 1024 > (da1:ahc0:0:5:0): Queuing a BDR SCB > (da1:ahc0:0:5:0): Bus Device Reset Message Sent > (da1:ahc0:0:5:0): no longer in timeout, status = 34b > ahc0: Bus Device Reset on A:5. 2 SCBs aborted I've downgraded the SCSI Sync Negotiation (from the SCSI BIOS) to 80MB/s and the messages disappears but mysqld continue to end with signal 11 under stress test. Regards. ----- Massimo Lusetti Network Department Manager url: http://www.datacode.it e-mail: staff@datacode.it ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 12:37:45 2001 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 A537A37B71B for ; Mon, 12 Mar 2001 12:37:43 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2CKbUs37941; Mon, 12 Mar 2001 13:37:30 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103122037.f2CKbUs37941@aslan.scsiguy.com> To: "Massimo Lusetti" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC-7892 & Ultra160 problems In-Reply-To: Your message of "Mon, 12 Mar 2001 21:32:47 +0100." <006b01c0ab33$99842530$0d01a8c0@local.lan> Date: Mon, 12 Mar 2001 13:37:30 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >Firt of all Hi everyone cause this is my first message to this list, ok i >can go on now... > >I got a new fresh IBM Netfinity x220 series machine which has a AIC-7892 >SCSI controller integrated onboard, that my problems begin. What FreeBSD release are you running? What kind of disk are you using (firmware rev included)? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 13:30:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 6172437B719; Mon, 12 Mar 2001 13:30:09 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CLTM821468; Mon, 12 Mar 2001 13:29:22 -0800 (PST) Date: Mon, 12 Mar 2001 13:29:22 -0800 From: Alfred Perlstein To: Soren Schmidt Cc: Kevin Oberman , scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312132922.Y18351@fw.wintelcom.net> References: <20010312125905.X18351@fw.wintelcom.net> <200103122120.WAA10675@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122120.WAA10675@freebsd.dk>; from sos@freebsd.dk on Mon, Mar 12, 2001 at 10:20:32PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Moved to -scsi... Justin, as Mr. SCSI (can i call you that? :) ) I'd like to ask you something * Soren Schmidt [010312 13:20] wrote: > It seems Alfred Perlstein wrote: > > > > Prior to March 1 I could dd a 4 GB slice in 580 seconds (or a bit > > > > under 10 minutes). After March 1 the same exact command took just > > > > under 40 minutes to complete. The same was seen copying a 2 GB > > > > slice. It increased from 5 minutes to 20 minutes. No kernel > > > > configuration changes were made. > > > > > > This is worse than expected, try to use option ATA_ENABLE_WC > > > and see what gives, if its not back to normal we have to look elsewhere. > > > > Mr ATA, is there no ATA command to "syncronize cache" like in SCSI? > > Yes, there is, and the ATA driver even uses it, the problem is WHEN > to use it. I originally made it flush the cache if a write contained > the BIO_ORDERED bit, but that doesn't work with softupdates.. > If somebody can come up with a way to tell me when I need to flush > the write cache, then I'll happily add that.. Justin, I've heard that SCSI knows when to send sync-cache commands to the disks, how does the driver know when to do this based on the bio request? It'd be nice to get this fixed for 4.3 because I've noticed terrible perf for laptops because of the complete lack of write caching... :( -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 14:20: 2 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 5F80937B718; Mon, 12 Mar 2001 14:19:57 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id JAA18673; Tue, 13 Mar 2001 09:18:01 +1100 Date: Tue, 13 Mar 2001 09:17:47 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alfred Perlstein Cc: Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010312132922.Y18351@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Mar 2001, Alfred Perlstein wrote: > > > Mr ATA, is there no ATA command to "syncronize cache" like in SCSI? > > > > Yes, there is, and the ATA driver even uses it, the problem is WHEN > > to use it. I originally made it flush the cache if a write contained > > the BIO_ORDERED bit, but that doesn't work with softupdates.. > > If somebody can come up with a way to tell me when I need to flush > > the write cache, then I'll happily add that.. > > Justin, I've heard that SCSI knows when to send sync-cache commands > to the disks, how does the driver know when to do this based on > the bio request? > > It'd be nice to get this fixed for 4.3 because I've noticed terrible > perf for laptops because of the complete lack of write caching... :( I just put "options ATA_ENABLE_WC" in all my config files. Changing the default for write caching from enabled to disabled in rev.1.92 of ata_disk.c was a huge pessimisation, but it is probably currently required for soft updates. I don't use soft updates ... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 14:23:50 2001 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 98FAD37B71A for ; Mon, 12 Mar 2001 14:23:46 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2CMNMs39959; Mon, 12 Mar 2001 15:23:22 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103122223.f2CMNMs39959@aslan.scsiguy.com> To: Alfred Perlstein Cc: Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Mon, 12 Mar 2001 13:29:22 PST." <20010312132922.Y18351@fw.wintelcom.net> Date: Mon, 12 Mar 2001 15:23:22 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Moved to -scsi... > >Justin, as Mr. SCSI (can i call you that? :) ) I'd like to ask you >something Although my domain name may confuse people, I'm just *A* SCSI Guy, not *the* SCSI Guy. I think "Mr." is too close to the latter. >> > > This is worse than expected, try to use option ATA_ENABLE_WC >> > > and see what gives, if its not back to normal we have to look elsewhere. >> > >> > Mr ATA, is there no ATA command to "syncronize cache" like in SCSI? >> >> Yes, there is, and the ATA driver even uses it, the problem is WHEN >> to use it. I originally made it flush the cache if a write contained >> the BIO_ORDERED bit, but that doesn't work with softupdates.. >> If somebody can come up with a way to tell me when I need to flush > the write cache, then I'll happily add that.. > >Justin, I've heard that SCSI knows when to send sync-cache commands >to the disks, how does the driver know when to do this based on >the bio request? We don't do anything so fancy. On final close, a synchronize cache command is issued. We don't actively enable or disable write caching, but instead leave this up to the user to configure (via camcontrol or, in some cases, through their controller's BIOS). SCSI also provides "Force Unit Access" that is settable on a per-command basis, but I don't know that the SCSI spec is clear on whether having an ordered tagged transaction complete that has the FUA bit set guarantees that all previous commands have actually hit the disk. Even if the spec did, it would be dangerous to assume that all devices are compliant. I do believe, however, that SCSI does guarantee that, even with write caching enabled, an ordered tagged transaction will only appear on the media after all transactions queued before it have been committed. Again, whether a particular drive honors this is anyones guess. As for dd, it is not a great test of the true impact of disabling write caching. dd pays a high latency penalty because it completely serializes transactions to the disk. When going through the filesystem, writes are performed in batches without preventing other transactions from occurring in the mean time. This is when tagged queuing really pays off. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 14:56:28 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 347CB37B71A for ; Mon, 12 Mar 2001 14:56:16 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 14cbDr-0000SR-00; Mon, 12 Mar 2001 14:55:27 -0800 Date: Mon, 12 Mar 2001 14:55:24 -0800 (PST) From: Tom Samplonius To: Massimo Lusetti Cc: freebsd-scsi@freebsd.org Subject: Re: AIC-7892 & Ultra160 problems In-Reply-To: <006b01c0ab33$99842530$0d01a8c0@local.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Mar 2001, Massimo Lusetti wrote: ... > I've downgraded the SCSI Sync Negotiation (from the SCSI BIOS) to 80MB/s and > the messages disappears but mysqld continue to end with signal 11 under > stress test. You don't mention the version, but if you are using 4.2-RELEASE, then that is a known problem. 4.2-STABLE has had a fix for the mysql issue for quite while. > Regards. > ----- > Massimo Lusetti > Network Department Manager > > url: http://www.datacode.it > e-mail: staff@datacode.it > ----- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 15: 7:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7445237B719; Mon, 12 Mar 2001 15:07:46 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CN6Ne24881; Mon, 12 Mar 2001 15:06:23 -0800 (PST) Date: Mon, 12 Mar 2001 15:06:23 -0800 From: Alfred Perlstein To: Bruce Evans Cc: Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312150623.D18351@fw.wintelcom.net> References: <20010312132922.Y18351@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Tue, Mar 13, 2001 at 09:17:47AM +1100 X-all-your-base: are belong to us. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Bruce Evans [010312 14:18] wrote: > On Mon, 12 Mar 2001, Alfred Perlstein wrote: > > > > > Mr ATA, is there no ATA command to "syncronize cache" like in SCSI? > > > > > > Yes, there is, and the ATA driver even uses it, the problem is WHEN > > > to use it. I originally made it flush the cache if a write contained > > > the BIO_ORDERED bit, but that doesn't work with softupdates.. > > > If somebody can come up with a way to tell me when I need to flush > > > the write cache, then I'll happily add that.. > > > > Justin, I've heard that SCSI knows when to send sync-cache commands > > to the disks, how does the driver know when to do this based on > > the bio request? > > > > It'd be nice to get this fixed for 4.3 because I've noticed terrible > > perf for laptops because of the complete lack of write caching... :( > > I just put "options ATA_ENABLE_WC" in all my config files. Changing > the default for write caching from enabled to disabled in rev.1.92 of > ata_disk.c was a huge pessimisation, but it is probably currently > required for soft updates. I don't use soft updates ... Afaik it's also required by normal non-async mounts. Basically if you let the disk lie about write completetion you might as well be running fully async. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 15:11:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E4F0237B71A for ; Mon, 12 Mar 2001 15:11:43 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CNAO425021; Mon, 12 Mar 2001 15:10:24 -0800 (PST) Date: Mon, 12 Mar 2001 15:10:24 -0800 From: Alfred Perlstein To: "Justin T. Gibbs" Cc: Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312151024.E18351@fw.wintelcom.net> References: <20010312132922.Y18351@fw.wintelcom.net> <200103122223.f2CMNMs39959@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122223.f2CMNMs39959@aslan.scsiguy.com>; from gibbs@scsiguy.com on Mon, Mar 12, 2001 at 03:23:22PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Justin T. Gibbs [010312 14:23] wrote: > >Moved to -scsi... > > > >Justin, as Mr. SCSI (can i call you that? :) ) I'd like to ask you > >something > > Although my domain name may confuse people, I'm just *A* SCSI Guy, > not *the* SCSI Guy. I think "Mr." is too close to the latter. Ah, take it like a man. :) > >> > > This is worse than expected, try to use option ATA_ENABLE_WC > >> > > and see what gives, if its not back to normal we have to look elsewhere. > >> > > >> > Mr ATA, is there no ATA command to "syncronize cache" like in SCSI? > >> > >> Yes, there is, and the ATA driver even uses it, the problem is WHEN > >> to use it. I originally made it flush the cache if a write contained > >> the BIO_ORDERED bit, but that doesn't work with softupdates.. > >> If somebody can come up with a way to tell me when I need to flush > > the write cache, then I'll happily add that.. > > > >Justin, I've heard that SCSI knows when to send sync-cache commands > >to the disks, how does the driver know when to do this based on > >the bio request? > > We don't do anything so fancy. On final close, a synchronize cache > command is issued. We don't actively enable or disable write caching, > but instead leave this up to the user to configure (via camcontrol or, > in some cases, through their controller's BIOS). SCSI also provides > "Force Unit Access" that is settable on a per-command basis, but I don't > know that the SCSI spec is clear on whether having an ordered tagged > transaction complete that has the FUA bit set guarantees that all > previous commands have actually hit the disk. Even if the spec did, > it would be dangerous to assume that all devices are compliant. I > do believe, however, that SCSI does guarantee that, even with write > caching enabled, an ordered tagged transaction will only appear on > the media after all transactions queued before it have been committed. > Again, whether a particular drive honors this is anyones guess. > > As for dd, it is not a great test of the true impact of disabling > write caching. dd pays a high latency penalty because it completely > serializes transactions to the disk. When going through the filesystem, > writes are performed in batches without preventing other transactions > from occurring in the mean time. This is when tagged queuing really > pays off. TMI dude. :) All i need to know is if there's a way to look at a particular struct bio/buf and determine if there's a need to write the data sync. Soren claims that B_ORDERED is not the magic bit that's needed, is there one? Or are we SOL on the kernel communicating the need for a block to be written "right now" and not complete until sync'd to the backing storage's non-volatile media? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 15:19:23 2001 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 A979E37B71B for ; Mon, 12 Mar 2001 15:19:19 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2CNJ8s42439; Mon, 12 Mar 2001 16:19:08 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103122319.f2CNJ8s42439@aslan.scsiguy.com> To: Alfred Perlstein Cc: Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Mon, 12 Mar 2001 15:10:24 PST." <20010312151024.E18351@fw.wintelcom.net> Date: Mon, 12 Mar 2001 16:19:08 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >All i need to know is if there's a way to look at a particular >struct bio/buf and determine if there's a need to write the >data sync. Soren claims that B_ORDERED is not the magic bit that's >needed, is there one? Or are we SOL on the kernel communicating the >need for a block to be written "right now" and not complete until >sync'd to the backing storage's non-volatile media? Most, if not all, of the kernel assumes that the data is committed to non-volatile storage when the write is notified as complete. FFS and softupdates could survive if they marked meta data or the first buffer across a dependency domain respectively as B_ORDERED assuming the device commits to media in the expected order, but softupdates doesn't do this, and FFS probably doesn't do this correctly. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 15:24:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 84D2D37B71A; Mon, 12 Mar 2001 15:24:43 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CNNOS25501; Mon, 12 Mar 2001 15:23:24 -0800 (PST) Date: Mon, 12 Mar 2001 15:23:24 -0800 From: Alfred Perlstein To: "Justin T. Gibbs" Cc: Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312152324.H18351@fw.wintelcom.net> References: <20010312151024.E18351@fw.wintelcom.net> <200103122319.f2CNJ8s42439@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122319.f2CNJ8s42439@aslan.scsiguy.com>; from gibbs@scsiguy.com on Mon, Mar 12, 2001 at 04:19:08PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org cc'd -fs and Matt. :) * Justin T. Gibbs [010312 15:19] wrote: > >All i need to know is if there's a way to look at a particular > >struct bio/buf and determine if there's a need to write the > >data sync. Soren claims that B_ORDERED is not the magic bit that's > >needed, is there one? Or are we SOL on the kernel communicating the > >need for a block to be written "right now" and not complete until > >sync'd to the backing storage's non-volatile media? > > Most, if not all, of the kernel assumes that the data is committed to > non-volatile storage when the write is notified as complete. FFS > and softupdates could survive if they marked meta data or the first > buffer across a dependency domain respectively as B_ORDERED assuming > the device commits to media in the expected order, but softupdates > doesn't do this, and FFS probably doesn't do this correctly. Hmm, it wouldn't be that hard to have the bwrite() functions something with the buf that says, I'm waiting for this to complete and it damn better be complete when i get it back. (*) The ones that wait for completetion rather than bawrite() which just asks for an async write. The only problem with this is that sometimes bwrite is used when there's a shortage and it'd be nice to be able to take advantage of write caching in those instances. Hopefully one of us will look into it one of these days. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 15:34: 7 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E29FF37B71B; Mon, 12 Mar 2001 15:33:59 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA04673; Mon, 12 Mar 2001 15:33:40 -0800 Date: Mon, 12 Mar 2001 15:33:37 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alfred Perlstein Cc: "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010312152324.H18351@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > cc'd -fs and Matt. :) > > * Justin T. Gibbs [010312 15:19] wrote: > > >All i need to know is if there's a way to look at a particular > > >struct bio/buf and determine if there's a need to write the > > >data sync. Soren claims that B_ORDERED is not the magic bit that's > > >needed, is there one? Or are we SOL on the kernel communicating the > > >need for a block to be written "right now" and not complete until > > >sync'd to the backing storage's non-volatile media? > > > > Most, if not all, of the kernel assumes that the data is committed to > > non-volatile storage when the write is notified as complete. FFS > > and softupdates could survive if they marked meta data or the first > > buffer across a dependency domain respectively as B_ORDERED assuming > > the device commits to media in the expected order, but softupdates > > doesn't do this, and FFS probably doesn't do this correctly. > > Hmm, it wouldn't be that hard to have the bwrite() functions > something with the buf that says, I'm waiting for this to complete > and it damn better be complete when i get it back. Ordered tags, I believe, just guarantee the order in which things are done. If you have caching enable, then you'd better have something else which does send a Synchronize Cache. Oh- I take it back- you don't need a separate command. You can actually set a bit in the WRITE command that forces things out to media. So, what you really need to do is set both B_ORDERED and a new B_FLUSH (say) if you want to not only guarantee a barrier between this op and ones that follow, but also force this op to go to disk. You could also do a Head of Queue tag if you want to guarantee that this op goes to disk write away (ahead of everyone else). If you need everything sync'd, you'll have to explicitly have the da driver send the SYNCHRONIZE CACHE command. > (*) > The ones that wait for completetion rather than bawrite() which > just asks for an async write. > > The only problem with this is that sometimes bwrite is used when > there's a shortage and it'd be nice to be able to take advantage > of write caching in those instances. > > Hopefully one of us will look into it one of these days. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 15:46:20 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id F0CD937B718; Mon, 12 Mar 2001 15:46:11 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CNiq126258; Mon, 12 Mar 2001 15:44:52 -0800 (PST) Date: Mon, 12 Mar 2001 15:44:52 -0800 From: Alfred Perlstein To: Matthew Jacob Cc: "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312154452.K18351@fw.wintelcom.net> References: <20010312152324.H18351@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Mon, Mar 12, 2001 at 03:33:37PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Matthew Jacob [010312 15:33] wrote: > > > > cc'd -fs and Matt. :) > > > > * Justin T. Gibbs [010312 15:19] wrote: > > > >All i need to know is if there's a way to look at a particular > > > >struct bio/buf and determine if there's a need to write the > > > >data sync. Soren claims that B_ORDERED is not the magic bit that's > > > >needed, is there one? Or are we SOL on the kernel communicating the > > > >need for a block to be written "right now" and not complete until > > > >sync'd to the backing storage's non-volatile media? > > > > > > Most, if not all, of the kernel assumes that the data is committed to > > > non-volatile storage when the write is notified as complete. FFS > > > and softupdates could survive if they marked meta data or the first > > > buffer across a dependency domain respectively as B_ORDERED assuming > > > the device commits to media in the expected order, but softupdates > > > doesn't do this, and FFS probably doesn't do this correctly. > > > > Hmm, it wouldn't be that hard to have the bwrite() functions > > something with the buf that says, I'm waiting for this to complete > > and it damn better be complete when i get it back. > > Ordered tags, I believe, just guarantee the order in which things are done. If > you have caching enable, then you'd better have something else which does send > a Synchronize Cache. > > Oh- I take it back- you don't need a separate command. You can actually set a > bit in the WRITE command that forces things out to media. > > So, what you really need to do is set both B_ORDERED and a new B_FLUSH > (say) if you want to not only guarantee a barrier between this op and ones > that follow, but also force this op to go to disk. > > You could also do a Head of Queue tag if you want to guarantee that this op > goes to disk write away (ahead of everyone else). > > If you need everything sync'd, you'll have to explicitly have the da driver > send the SYNCHRONIZE CACHE command. Afaik we never depend on actually B_ORDERED'd data, at least not for filesystem consistancy (as afaik it would violate USL patents). We really don't need the SYNCHRONIZE CACHE either, basically a B_FLUSH would be nice, the problem I see is making sure it doesn't get eaten by the millions :) of OR's and AND's on the b_flags fields. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 15:53:32 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CDE8F37B71A; Mon, 12 Mar 2001 15:53:24 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA04726; Mon, 12 Mar 2001 15:53:13 -0800 Date: Mon, 12 Mar 2001 15:53:10 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alfred Perlstein Cc: "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010312154452.K18351@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > If you need everything sync'd, you'll have to explicitly have the da driver > > send the SYNCHRONIZE CACHE command. > > Afaik we never depend on actually B_ORDERED'd data, at least not > for filesystem consistancy (as afaik it would violate USL patents). Hmm? Wasn't there an assertion about this from Terry IIRC? Huh.. as far as I remember Steve Kleiman was talking about this at Sun in 1990- dunno if this has any pertinence to the patent or usage. > We really don't need the SYNCHRONIZE CACHE either, basically a B_FLUSH > would be nice, the problem I see is making sure it doesn't get eaten > by the millions :) of OR's and AND's on the b_flags fields. Well, if I understood your mail, you were trying to find out a way to live safely with not only ordering (which is done in s/w with softupdates for FreeBSD, right?- last I heard from Steve Tweedie was that he was considering using tags for ordering in ext3) but also to try and live safely with data that is cached on the drive electronics but not committed to media yet. Did I misunderstand your questions to Justin? It's quite possible as I've been switching between 5 different systems I'm working on today and I'm sure that things didn't committed to &my& media before things were wiped as switched from one KDE desktop to another..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 16: 9:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BC67337B71A; Mon, 12 Mar 2001 16:09:20 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2D07he27097; Mon, 12 Mar 2001 16:07:43 -0800 (PST) Date: Mon, 12 Mar 2001 16:07:43 -0800 From: Alfred Perlstein To: Matthew Jacob Cc: "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312160742.L18351@fw.wintelcom.net> References: <20010312154452.K18351@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Mon, Mar 12, 2001 at 03:53:10PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Matthew Jacob [010312 15:53] wrote: > > > If you need everything sync'd, you'll have to explicitly have the da driver > > > send the SYNCHRONIZE CACHE command. > > > > Afaik we never depend on actually B_ORDERED'd data, at least not > > for filesystem consistancy (as afaik it would violate USL patents). > > Hmm? Wasn't there an assertion about this from Terry IIRC? Huh.. as far as I > remember Steve Kleiman was talking about this at Sun in 1990- dunno if this > has any pertinence to the patent or usage. > > > We really don't need the SYNCHRONIZE CACHE either, basically a B_FLUSH > > would be nice, the problem I see is making sure it doesn't get eaten > > by the millions :) of OR's and AND's on the b_flags fields. > > Well, if I understood your mail, you were trying to find out a way to live > safely with not only ordering (which is done in s/w with softupdates for > FreeBSD, right?- last I heard from Steve Tweedie was that he was considering > using tags for ordering in ext3) but also to try and live safely with data > that is cached on the drive electronics but not committed to media yet. > > Did I misunderstand your questions to Justin? It's quite possible as I've been > switching between 5 different systems I'm working on today and I'm sure that > things didn't committed to &my& media before things were wiped as switched > from one KDE desktop to another..... Your previous paragraph "Well, if I understood your mail" is what I was looking for. Basically I was inquiring if the hardware could/would support a request to perform a write-through or not lie about the write completing for certain tagged writes. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 16:19:54 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A38E937B718; Mon, 12 Mar 2001 16:19:47 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA04885; Mon, 12 Mar 2001 16:18:44 -0800 Date: Mon, 12 Mar 2001 16:18:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alfred Perlstein Cc: "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010312160742.L18351@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > We really don't need the SYNCHRONIZE CACHE either, basically a B_FLUSH > > > would be nice, the problem I see is making sure it doesn't get eaten > > > by the millions :) of OR's and AND's on the b_flags fields. > > > > Well, if I understood your mail, you were trying to find out a way to live > > safely with not only ordering (which is done in s/w with softupdates for > > FreeBSD, right?- last I heard from Steve Tweedie was that he was considering > > using tags for ordering in ext3) but also to try and live safely with data > > that is cached on the drive electronics but not committed to media yet. > > > > Did I misunderstand your questions to Justin? It's quite possible as I've been > > switching between 5 different systems I'm working on today and I'm sure that > > things didn't committed to &my& media before things were wiped as switched > > from one KDE desktop to another..... > > Your previous paragraph "Well, if I understood your mail" is what I was > looking for. Basically I was inquiring if the hardware could/would > support a request to perform a write-through or not lie about the > write completing for certain tagged writes. There's no 'lying' here- the writes are completing. Those are "done" operations. It just depends on the mode you've set the disk (or tape, for that matter, which is usual) whether or not done means "on media" or "in drive cache". These operations are so done, in fact, that if there is an error later in putting them to media itself, there'll be all kinds of interesting toe stubbing going on. What I referred to in my previous mail is setting the FUA bit in the write. In the SCSI-2 spec, section 9.1.6, one paragraph states, in part: ...For a write operation, setting FUA to one causes the direct-access device to complete the data write to the physical medium before completing the command.... Does think this sounds like what you wan? You can also force data to not be in the drive cache as well (even when committed to media), so you can do things like not blow your drive cache on data you don't expect to need to re-read for a while- but this is cleverer than what is needed. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 17:10:10 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BF51A37B719; Mon, 12 Mar 2001 17:09:56 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2D196Q29022; Mon, 12 Mar 2001 17:09:06 -0800 (PST) Date: Mon, 12 Mar 2001 17:09:05 -0800 From: Alfred Perlstein To: Matthew Jacob Cc: "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312170905.O18351@fw.wintelcom.net> References: <20010312160742.L18351@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Mon, Mar 12, 2001 at 04:18:41PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Matthew Jacob [010312 16:18] wrote: > > > > > We really don't need the SYNCHRONIZE CACHE either, basically a B_FLUSH > > > > would be nice, the problem I see is making sure it doesn't get eaten > > > > by the millions :) of OR's and AND's on the b_flags fields. > > > > > > Well, if I understood your mail, you were trying to find out a way to live > > > safely with not only ordering (which is done in s/w with softupdates for > > > FreeBSD, right?- last I heard from Steve Tweedie was that he was considering > > > using tags for ordering in ext3) but also to try and live safely with data > > > that is cached on the drive electronics but not committed to media yet. > > > > > > Did I misunderstand your questions to Justin? It's quite possible as I've been > > > switching between 5 different systems I'm working on today and I'm sure that > > > things didn't committed to &my& media before things were wiped as switched > > > from one KDE desktop to another..... > > > > Your previous paragraph "Well, if I understood your mail" is what I was > > looking for. Basically I was inquiring if the hardware could/would > > support a request to perform a write-through or not lie about the > > write completing for certain tagged writes. > > There's no 'lying' here- the writes are completing. Those are "done" > operations. It just depends on the mode you've set the disk (or tape, for that > matter, which is usual) whether or not done means "on media" or "in drive > cache". These operations are so done, in fact, that if there is an error later > in putting them to media itself, there'll be all kinds of interesting toe > stubbing going on. > > What I referred to in my previous mail is setting the FUA bit in the write. > > In the SCSI-2 spec, section 9.1.6, one paragraph states, in part: > > ...For a write operation, setting FUA to one causes the direct-access > device to complete the data write to the physical medium before > completing the command.... Being able to tell the driver to do this from software would be the best. This would allow us to use writecaching for data, but force stable storage for meta-data. I think we'd also want to use this for forced data sync (fsync(2) and files opened with O_SYNC). > Does think this sounds like what you wan? Yes. > You can also force data to not be in > the drive cache as well (even when committed to media), so you can do things > like not blow your drive cache on data you don't expect to need to re-read for > a while- but this is cleverer than what is needed. This looks like an optimization that could be used for things like physio and probably any case mentioned above (B_PUSH). -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 18: 4:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cs4.cs.ait.ac.th (cs4.cs.ait.ac.th [192.41.170.16]) by hub.freebsd.org (Postfix) with ESMTP id 7BAB837B739 for ; Mon, 12 Mar 2001 18:03:54 -0800 (PST) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5]) by cs4.cs.ait.ac.th (8.9.3/8.9.3) with ESMTP id JAA18611; Tue, 13 Mar 2001 09:03:19 +0700 (GMT+0700) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.8.5/8.8.5) id JAA11318; Tue, 13 Mar 2001 09:03:29 +0700 (ICT) Date: Tue, 13 Mar 2001 09:03:29 +0700 (ICT) Message-Id: <200103130203.JAA11318@banyan.cs.ait.ac.th> X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f From: Olivier Nicole To: groudier@club-internet.fr Cc: gemorga2@vt.edu, mjacob@feral.com, freebsd-scsi@FreeBSD.ORG In-reply-to: (message from =?ISO-8859-1?Q?G=E9rard_Roudier?= on Mon, 12 Mar 2001 18:52:08 +0100 (CET)) Subject: Re: SCSI speed with SLR100 tape drive References: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerard, >Could you please, post _all_ the messages printed out by the sym driver? I hope that's what you mean: sym0: <896> port 0xb800-0xb8ff mem 0xfa000000-0xfa001fff,0xfa800000-0xfa8003ff i rq 10 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-40, 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. sym1: <896> port 0xb400-0xb4ff mem 0xf9000000-0xf9001fff,0xf9800000-0xf98003ff i rq 11 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. [...] Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. sa0 at sym1 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da4 at sym0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da3 at sym0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Disk are on SCSI bus 0, tape alone on bus 1. It looks pretty much it is LVD. When using the Symbios Configuration Utility it says: SCSI 2 Identification TANDGBERGSLR100 0402 MB/sec 80 MT/sec 40 data width 16 scan ID yes scan LUNs>0 yes disconnect on timeout 10 queue tags on boot choice no Above information are similar for disk and bus controler, except the SCSI target and the identification string. >May-be 40 MB/s burst is already enough to feed the tape fast enough to >allow it to stream data. It is actually, just I am trying to understand. In fact I got the drive but there is a shortage of media... The wonders of living in far East :) Merci, Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 20: 5:16 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 56E9737B719; Mon, 12 Mar 2001 20:05:09 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id UAA12199; Mon, 12 Mar 2001 20:59:11 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpdAAAG5aiOx; Mon Mar 12 20:59:01 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA03536; Mon, 12 Mar 2001 21:04:44 -0700 (MST) From: Terry Lambert Message-Id: <200103130404.VAA03536@usr05.primenet.com> Subject: Re: Disk I/O problem in 4.3-BETA To: mjacob@feral.com Date: Tue, 13 Mar 2001 04:04:38 +0000 (GMT) Cc: bright@wintelcom.net (Alfred Perlstein), gibbs@scsiguy.com (Justin T. Gibbs), sos@freebsd.dk (Soren Schmidt), oberman@es.net (Kevin Oberman), scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG In-Reply-To: from "Matthew Jacob" at Mar 12, 2001 03:53:10 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Afaik we never depend on actually B_ORDERED'd data, at least not > > for filesystem consistancy (as afaik it would violate USL patents). > > Hmm? Wasn't there an assertion about this from Terry IIRC? Huh.. as far as I > remember Steve Kleiman was talking about this at Sun in 1990- dunno if this > has any pertinence to the patent or usage. Depends on how you use them; the actual assignee was Novell; I got to see the filing materials back in 1993, when I was a Novell/USG (former USL, from the Novell side) attributed FS guru; see: US5642501:Computer method and apparatus for asynchronous ordered operations http://www.delphion.com/details?pn=US05642501__ US5666532:Computer method and apparatus for asynchronous ordered operations http://www.delphion.com/details?pn=US05666532__ Be warned; they are 175 and 34 pages, respectively. > Did I misunderstand your questions to Justin? It's quite possible as I've been > switching between 5 different systems I'm working on today and I'm sure that > things didn't committed to &my& media before things were wiped as switched > from one KDE desktop to another..... I think Alfred just wants them to be forced to stable storage before a dependency is considered statisfied; if so, there's no patent issue with D.O.W. (Delayed Ordered Writes). There might be an issue with one of the claims in the first patent, if you were to do write gathering, like Alfred had suggested. Doing that would be a mistake anyway: you might as well mount the thing async if you are going to write cache dependencies such that they aren't committed in the correct order, and a partial commit would then be possible. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 12 23:48:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.comm2000.it (mindseal.comm2000.it [194.133.0.6]) by hub.freebsd.org (Postfix) with ESMTP id 15B6537B718 for ; Mon, 12 Mar 2001 23:48:24 -0800 (PST) (envelope-from m.lusetti@datacode.it) Received: from purtroppo.local.lan ([212.97.62.126]) by relay.comm2000.it (8.11.2/MFAGMM-19990726) with ESMTP id f2D7mMH17325; Tue, 13 Mar 2001 08:48:22 +0100 X-SMTP-Peer: [212.97.62.126] Received: from massimo (massimo.local.lan [192.168.1.13]) by purtroppo.local.lan (8.11.1/8.11.1) with SMTP id f2D7m9Q04962; Tue, 13 Mar 2001 08:48:09 +0100 (CET) (envelope-from m.lusetti@datacode.it) Message-ID: <001401c0ab91$fd26a5f0$0d01a8c0@local.lan> From: "Massimo Lusetti" To: "Justin T. Gibbs" Cc: References: <200103122037.f2CKbUs37941@aslan.scsiguy.com> Subject: Re: AIC-7892 & Ultra160 problems Date: Tue, 13 Mar 2001 08:48:00 +0100 Organization: DATACODE s.r.l. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----- Original Message ----- From: "Justin T. Gibbs" To: "Massimo Lusetti" Cc: Sent: Monday, March 12, 2001 9:37 PM Subject: Re: AIC-7892 & Ultra160 problems > What FreeBSD release are you running? > Well, sorry for missing information. Anyway i've installed FreeBSD 4.2-RELEASE from CD-ROM set. > What kind of disk are you using (firmware rev included)? > I've three identical drives. FreeBSD recognize this way: da0 at ahc0 bus 0 target 4 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 5 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da2 at ahc0 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Just one more info, again after the downgrade to 80MB/s from SCSI bios sync negotiation i get the same error this morning... Regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 8:28:35 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mx10.quantum.com (mx10.quantum.com [204.212.103.176]) by hub.freebsd.org (Postfix) with ESMTP id 7CFE837B721; Tue, 13 Mar 2001 08:28:25 -0800 (PST) (envelope-from Stephen.Byan@quantum.com) Received: from milcmima.qntm.com (milcmima.qntm.com [146.174.18.61]) by mx10.quantum.com (8.9.3+Sun/8.9.3) with ESMTP id IAA22570; Tue, 13 Mar 2001 08:24:53 -0800 (PST) Received: by milcmima.qntm.com with Internet Mail Service (5.5.2650.21) id ; Tue, 13 Mar 2001 08:26:17 -0800 Message-ID: <38E52A0B1357D411A42400805FA79384019631CE@shrcmsgb.tdh.qntm.com> From: Stephen Byan To: "'Alfred Perlstein'" , Matthew Jacob Cc: "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: RE: Disk I/O problem in 4.3-BETA Date: Tue, 13 Mar 2001 08:26:10 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alfred Perlstein [mailto:bright@wintelcom.net] wrote: > This would allow us to use writecaching for data, but force > stable storage for meta-data. I think we'd also want to use > this for forced data sync (fsync(2) and files opened with O_SYNC). I do hope this gets implemented. I did something similar at Hitachi in our OSF/1 port to the S/390 back around 1992. The disk controllers had a substantial amount of volatile RAM cache, and a lesser amount of NV-RAM cache. We directed the metadata writes to NV-RAM, and the data to volatile cache (with a flush at partition close, of course). Since the hit rate on metadata writes in UFS is very high, even with a small NV cache, we were able to get substantial speedups in metadata intensive operations such as a recursive directory copy. We also implemented sequential I/O hinting, detected by the read-ahead mechanism in the file system. Passing this hint down allowed the controller to do a better job of cache management: sequential I/O recycled the buffers after they had been read or written, rather than aging them through the LRU list, so sequential reads and writes didn't trash the cache. For NFS v2, it's also helpful to be able to mark the write I/O's as non-cachable, thus hinting them toward NV-RAM. In Windows NT, NTFS uses the SCSI Force Unit Access (FUA) bit on it's metadata writes (log writes for sure; it should also use FUA for lazy writes of metadata, else there is a race condition for recycling the log entry, no?, but I don't know whether it actually uses FUA for lazy writes of metadata). It doesn't hint the SCSI CDBs with sequential access information, but such info is available in the IRP presented to the SCSI class driver, and a filter driver could do some magic... If NT and FreeBSD both support hinting of metadata writes, it's only a matter of time before the hardware support appears. Regards, -Steve Steve Byan Design Engineer Quantum Corporation MS 1-3/E23 333 South Street Shrewsbury, MA 01545 (508)770-3414 fax: (508)770-2604 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 8:37:58 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.136]) by hub.freebsd.org (Postfix) with ESMTP id 2ADAC37B718; Tue, 13 Mar 2001 08:37:54 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.9.3/8.9.3) with ESMTP id RAA45397; Tue, 13 Mar 2001 17:37:52 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f2DGcAp08823; Tue, 13 Mar 2001 17:38:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Stephen Byan Cc: "'Alfred Perlstein'" , Matthew Jacob , "Justin T. Gibbs" , Soren Schmidt , Kevin Oberman , scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Tue, 13 Mar 2001 08:26:10 PST." <38E52A0B1357D411A42400805FA79384019631CE@shrcmsgb.tdh.qntm.com> Date: Tue, 13 Mar 2001 17:38:10 +0100 Message-ID: <8821.984501490@critter> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >If NT and FreeBSD both support hinting of metadata writes, it's only a >matter of time before the hardware support appears. I have been looking for a long time for a PCI NVRAM card at a reasonable cost, anyone know of any with a reasonable price ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 10:39: 3 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 0AA7337B719; Tue, 13 Mar 2001 10:39:00 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f2DIcas00336; Tue, 13 Mar 2001 10:38:36 -0800 (PST) Message-Id: <200103131838.f2DIcas00336@ptavv.es.net> To: "Justin T. Gibbs" Cc: Alfred Perlstein , stable@freebsd.org, Soren Schmidt , scsi@freebsd.org Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Your message of "Mon, 12 Mar 2001 15:23:22 MST." <200103122223.f2CMNMs39959@aslan.scsiguy.com> Date: Tue, 13 Mar 2001 10:38:36 -0800 From: "Kevin Oberman" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to everyone. I had no idea what an interesting thread I was spawning with my original question. Since I now understand just how dangerous running BOTH WC and SOFTUPDATES can be, I have rebuilt my kernel with WC disabled and, for a reasonably fast backup, where WC is not a data integrity issue, I have a special kernel with WC enabled. I'll just live with the slow-down in things unless smarter folks figure a way to make write cache work safely. Sometimes speed is not everything. When I brought up my first FreeBSD system I had a bad memory card which caused several crashes and hopelessly corrupted my disk. This was no big thing as I had a virgin install and it was easy to just re-install after replacing the bad RAM. But I'd find that to be a real pain today. (And I DO have a good backup today.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 11:45: 9 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from hoku.2y.net (a204b210n98client170.hawaii.rr.com [204.210.98.170]) by hub.freebsd.org (Postfix) with ESMTP id D120F37B723 for ; Tue, 13 Mar 2001 11:44:59 -0800 (PST) (envelope-from terrance@hoku.2y.net) Received: from localhost (terrance@localhost) by hoku.2y.net (8.11.1/8.11.1) with ESMTP id f2DJiqw00417 for ; Tue, 13 Mar 2001 09:44:53 -1000 (HST) (envelope-from terrance@hoku.2y.net) Date: Tue, 13 Mar 2001 09:44:38 -1000 (HST) From: Terrance Young To: freebsd-scsi@FreeBSD.ORG Subject: Buslogic Flashpoint LT PCI SCSI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org HI, Has anyone done any work for a driver for the Buslogic Flashpoint LT PCI SCSI card? If so I'd be glad to help in anyway I can. I have two such cards and would be glad to do some testing or what ever I can do to help with this effort. Terrance To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 12:21:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from front3.grolier.fr (front3.grolier.fr [194.158.96.53]) by hub.freebsd.org (Postfix) with ESMTP id 3B2D237B719 for ; Tue, 13 Mar 2001 12:21:13 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from nas2-190.mea.club-internet.fr (nas2-190.mea.club-internet.fr [195.36.200.190]) by front3.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA22004; Tue, 13 Mar 2001 21:20:52 +0100 (MET) Date: Tue, 13 Mar 2001 19:10:21 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Olivier Nicole Cc: gemorga2@vt.edu, mjacob@feral.com, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI speed with SLR100 tape drive In-Reply-To: <200103130203.JAA11318@banyan.cs.ait.ac.th> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Olivier, I just dowloaded from Tandberg site the pdf document that contains the=20 technical specifications of the SLR100. (43203505.pdf). You can reach it by clicking 3 or 4 times appropriately.:) The SLR100 transfer rates are documented as follows: - 5 MB/s native sustained - 10 MB/s compressed sustained - 40 MB/s burst So, your tape device is actually operating at its maximum burst data rate, under FreeBSD. The Symbios BIOS device layout is what user wishes. What will be accepted by the device can be different. In our case, the driver is certainly negotiating for 40 MT/s wide =3D 80 MB/s, but the device lowers this speed in the response to 20 MT/s wide =3D 40 MB/s (wich is its maximum). Btw, if you donnot have the pdf document, let me know and I will send it you as attachment. Regards, G=E9rard. On Tue, 13 Mar 2001, Olivier Nicole wrote: > Gerard, >=20 > >Could you please, post _all_ the messages printed out by the sym driver? >=20 > I hope that's what you mean: >=20 > sym0: <896> port 0xb800-0xb8ff mem 0xfa000000-0xfa001fff,0xfa800000-0xfa8= 003ff i > rq 10 at device 5.0 on pci1 > sym0: Symbios NVRAM, ID 7, Fast-40, 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. > sym1: <896> port 0xb400-0xb4ff mem 0xf9000000-0xf9001fff,0xf9800000-0xf98= 003ff i > rq 11 at device 5.1 on pci1 > sym1: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking > sym1: open drain IRQ line driver, using on-chip SRAM > sym1: using LOAD/STORE-based firmware. > sym1: handling phase mismatch from SCRIPTS. > [...] > Waiting 15 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. > sa0 at sym1 bus 0 target 2 lun 0 > sa0: Removable Sequential Access SCSI-2 device=20 > sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device=20 > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da0: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > da4 at sym0 bus 0 target 4 lun 0 > da4: Fixed Direct Access SCSI-3 device=20 > da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da4: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > da3 at sym0 bus 0 target 3 lun 0 > da3: Fixed Direct Access SCSI-3 device=20 > da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da3: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > da2 at sym0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-3 device=20 > da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da2: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device=20 > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) >=20 > Disk are on SCSI bus 0, tape alone on bus 1. It looks pretty much it > is LVD. >=20 > When using the Symbios Configuration Utility it says: >=20 > SCSI=09 2 > Identification TANDGBERGSLR100 0402 > MB/sec=09 80 > MT/sec=09 40 > data width 16 > scan ID=09 yes > scan LUNs>0 yes > disconnect on > timeout=09 10 > queue tags on > boot choice no >=20 > Above information are similar for disk and bus controler, except the > SCSI target and the identification string. >=20 > >May-be 40 MB/s burst is already enough to feed the tape fast enough to > >allow it to stream data. >=20 > It is actually, just I am trying to understand. In fact I got the > drive but there is a shortage of media... The wonders of living in far > East :) >=20 >=20 > Merci, >=20 > Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 12:28:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id B688937B719; Tue, 13 Mar 2001 12:28:06 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA54718; Tue, 13 Mar 2001 14:28:03 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 13 Mar 2001 14:28:03 -0600 (CST) From: Chris Dillon To: Poul-Henning Kamp Cc: , Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <8821.984501490@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org CCs trimmed... On Tue, 13 Mar 2001, Poul-Henning Kamp wrote: > > >If NT and FreeBSD both support hinting of metadata writes, it's only a > >matter of time before the hardware support appears. > > I have been looking for a long time for a PCI NVRAM card at a > reasonable cost, anyone know of any with a reasonable price ? How "non-volatile" do you want it to be? I realize truly non-volatile means "forever" (i.e. Flash EEPROM, MRAM, or similar). However, a few minutes/hours (battery-backed volatile RAM) might be enough? The relatively cheap Mylex AcceleRAID 170 we just recently purchased has a "super-cap" (a very high-capacity capacitor, but not exactly a battery) on it, which could theoretically supply power to the on-board cache for at least a few minutes. The documentation and spec sheets for the board mention absolutely nothing about it, but its there. The low-profile version of the board doesn't appear to have the "super-cap", though. I've also got an AMI MegaRAID Enterprise 1200 at home with the small Ni-Cad battery backup module, and it should be able to keep the memory alive for at least a few hours. I think all of AMI's Enterprise level controllers offer that option. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 12:44:54 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.136]) by hub.freebsd.org (Postfix) with ESMTP id 09A5937B71D; Tue, 13 Mar 2001 12:44:50 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA48930; Tue, 13 Mar 2001 21:44:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f2DKj5p10188; Tue, 13 Mar 2001 21:45:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chris Dillon Cc: scsi@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Tue, 13 Mar 2001 14:28:03 CST." Date: Tue, 13 Mar 2001 21:45:05 +0100 Message-ID: <10186.984516305@critter> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Ch ris Dillon writes: >> I have been looking for a long time for a PCI NVRAM card at a >> reasonable cost, anyone know of any with a reasonable price ? > >How "non-volatile" do you want it to be? I would want something on the order of an day or so, to cover catastrophic failures. My ideal product would be a PCI card with some SRAM, and a holder for a 9v DURACELL. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 12:52: 7 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 7F5C337B71D; Tue, 13 Mar 2001 12:51:59 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14cvlu-000Nc7-00; Tue, 13 Mar 2001 20:51:58 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.2/8.11.2) id f2DKs5N04591; Tue, 13 Mar 2001 21:54:05 +0100 (CET) (envelope-from wkb) Date: Tue, 13 Mar 2001 21:54:05 +0100 From: Wilko Bulte To: Poul-Henning Kamp Cc: Chris Dillon , scsi@freebsd.org, fs@freebsd.org Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313215405.A4567@freebie.demon.nl> References: <10186.984516305@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <10186.984516305@critter>; from phk@critter.freebsd.dk on Tue, Mar 13, 2001 at 09:45:05PM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 13, 2001 at 09:45:05PM +0100, Poul-Henning Kamp wrote: > In message , Ch > ris Dillon writes: > > >> I have been looking for a long time for a PCI NVRAM card at a > >> reasonable cost, anyone know of any with a reasonable price ? > > > >How "non-volatile" do you want it to be? > > I would want something on the order of an day or so, to cover > catastrophic failures. > > My ideal product would be a PCI card with some SRAM, and a holder > for a 9v DURACELL. Sounds like a PCI Prestoserve card to me. DEC used to produce these. Price? Dunno, probably steep. But Prestoserve cards might find themselves now on the scrap heaps. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 13:27:26 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A06FC37B718 for ; Tue, 13 Mar 2001 13:27:23 -0800 (PST) (envelope-from mauri@inspiral.net) Received: from inspiral.net (tigris-isdn-99.uninet.ee [194.204.61.99]) by ns.uninet.ee (Postfix) with ESMTP id C10AB25805 for ; Tue, 13 Mar 2001 23:27:21 +0200 (EET) Message-ID: <3AAE9082.2B0B8BD@inspiral.net> Date: Tue, 13 Mar 2001 23:26:27 +0200 From: Lauri Laupmaa X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: scsi@FreeBSD.ORG Subject: OT: Re: Disk I/O problem in 4.3-BETA References: <200103122223.f2CMNMs39959@aslan.scsiguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" wrote: > command is issued. We don't actively enable or disable write caching, > but instead leave this up to the user to configure (via camcontrol or, Wouldn't it be good if we had /etc/rc.scsi and such options (like write cache, etc) settable in /etc/rc.conf ? L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 13:33: 2 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ECF5037B749 for ; Tue, 13 Mar 2001 13:32:50 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09465; Tue, 13 Mar 2001 13:32:47 -0800 Date: Tue, 13 Mar 2001 13:32:44 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Lauri Laupmaa Cc: scsi@FreeBSD.ORG Subject: Re: OT: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <3AAE9082.2B0B8BD@inspiral.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 13 Mar 2001, Lauri Laupmaa wrote: > "Justin T. Gibbs" wrote: > > > command is issued. We don't actively enable or disable write caching, > > but instead leave this up to the user to configure (via camcontrol or, > > Wouldn't it be good if we had /etc/rc.scsi and such options (like write > cache, etc) settable in /etc/rc.conf ? No. Let the application (filesystem or other) decide this policy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 13:36:57 2001 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 BA64A37B71A for ; Tue, 13 Mar 2001 13:36:54 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA89661; Tue, 13 Mar 2001 14:36:49 -0700 (MST) (envelope-from ken) Date: Tue, 13 Mar 2001 14:36:49 -0700 From: "Kenneth D. Merry" To: Lauri Laupmaa Cc: scsi@FreeBSD.ORG Subject: Re: OT: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313143649.A89606@panzer.kdm.org> References: <200103122223.f2CMNMs39959@aslan.scsiguy.com> <3AAE9082.2B0B8BD@inspiral.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3AAE9082.2B0B8BD@inspiral.net>; from mauri@inspiral.net on Tue, Mar 13, 2001 at 11:26:27PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 13, 2001 at 23:26:27 +0200, Lauri Laupmaa wrote: > "Justin T. Gibbs" wrote: > > > command is issued. We don't actively enable or disable write caching, > > but instead leave this up to the user to configure (via camcontrol or, > > Wouldn't it be good if we had /etc/rc.scsi and such options (like write cache, etc) > settable in /etc/rc.conf ? Well, at least write caching is permanantly settable in mode page 8 for SCSI disks. So there's no need to set it for every boot. As for other things, like tags, etc., they're usually set automatically, except for devices that need to be quirked. It would be nice if we had a loadable quirk mechanism, but that hasn't happened yet. 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 Tue Mar 13 13:40:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DEDAD37B72C for ; Tue, 13 Mar 2001 13:40:46 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09542; Tue, 13 Mar 2001 13:40:47 -0800 Date: Tue, 13 Mar 2001 13:40:44 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: OT: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010313143649.A89606@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > As for other things, like tags, etc., they're usually set automatically, > except for devices that need to be quirked. It would be nice if we had a > loadable quirk mechanism, but that hasn't happened yet. I've been trying to think about this. This should probably be done like hints, no? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 13:43:34 2001 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 F24BC37B719 for ; Tue, 13 Mar 2001 13:43:29 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA89801; Tue, 13 Mar 2001 14:43:27 -0700 (MST) (envelope-from ken) Date: Tue, 13 Mar 2001 14:43:27 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: scsi@FreeBSD.ORG Subject: Re: OT: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313144327.A89776@panzer.kdm.org> References: <20010313143649.A89606@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Mar 13, 2001 at 01:40:44PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 13, 2001 at 13:40:44 -0800, Matthew Jacob wrote: > > As for other things, like tags, etc., they're usually set automatically, > > except for devices that need to be quirked. It would be nice if we had a > > loadable quirk mechanism, but that hasn't happened yet. > > > I've been trying to think about this. This should probably be done like hints, > no? Probably so. We'd probably want to set it up so the user-supplied quirk table would get searched before the compiled-in kernel quirk table. 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 Tue Mar 13 13:46:40 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EEADE37B719 for ; Tue, 13 Mar 2001 13:46:37 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09598; Tue, 13 Mar 2001 13:46:39 -0800 Date: Tue, 13 Mar 2001 13:46:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: OT: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010313144327.A89776@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Probably so. We'd probably want to set it up so the user-supplied quirk > table would get searched before the compiled-in kernel quirk table. Yup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 13:49: 1 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.136]) by hub.freebsd.org (Postfix) with ESMTP id 44E3D37B71B; Tue, 13 Mar 2001 13:48:57 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.9.3/8.9.3) with ESMTP id WAA49915; Tue, 13 Mar 2001 22:48:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f2DLnDp10846; Tue, 13 Mar 2001 22:49:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Wilko Bulte Cc: Chris Dillon , scsi@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Tue, 13 Mar 2001 21:54:05 +0100." <20010313215405.A4567@freebie.demon.nl> Date: Tue, 13 Mar 2001 22:49:13 +0100 Message-ID: <10844.984520153@critter> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20010313215405.A4567@freebie.demon.nl>, Wilko Bulte writes: >> My ideal product would be a PCI card with some SRAM, and a holder >> for a 9v DURACELL. > >Sounds like a PCI Prestoserve card to me. DEC used to produce these. >Price? Dunno, probably steep. But Prestoserve cards might find themselves >now on the scrap heaps. Yeah, well, I can't rely on them showing up on eBay if I want to deploy them, can I ? :-( Anyone know a sympathetic hardware vendor who might be co-opted into producing a product if we promise to make FreeBSD users want one ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 15:34:25 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 3D00437B718; Tue, 13 Mar 2001 15:34:19 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id RAA58080; Tue, 13 Mar 2001 17:34:14 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 13 Mar 2001 17:34:13 -0600 (CST) From: Chris Dillon To: Poul-Henning Kamp Cc: Wilko Bulte , , Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <10844.984520153@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 13 Mar 2001, Poul-Henning Kamp wrote: > In message <20010313215405.A4567@freebie.demon.nl>, Wilko Bulte writes: > > >> My ideal product would be a PCI card with some SRAM, and a holder > >> for a 9v DURACELL. > > > >Sounds like a PCI Prestoserve card to me. DEC used to produce these. > >Price? Dunno, probably steep. But Prestoserve cards might find themselves > >now on the scrap heaps. > > Yeah, well, I can't rely on them showing up on eBay if I want to > deploy them, can I ? :-( > > Anyone know a sympathetic hardware vendor who might be co-opted into > producing a product if we promise to make FreeBSD users want one ? It should be fairly trivial to increase the battery capacity to cover your needs on the existing boards that already offer the ability, even by yourself, if not by the manufacturer itself. I've seen external RAID controllers that used 6V lead-acid batteries for the memory backup... at that point, it would be very easy to stick a larger battery (or batteries) in place to meet your needs. I'm not sure who makes PCI boards which use external batteries, though, nor ones that use low-power SRAM instead of DRAM (which would actually be a good application for the super-caps, since they could power the SRAM much longer than DRAM). -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 15:46: 4 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from eozoon.coleman.org (adsl-209-233-238-136.dsl.snfc21.pacbell.net [209.233.238.136]) by hub.freebsd.org (Postfix) with ESMTP id A545637B741; Tue, 13 Mar 2001 15:45:49 -0800 (PST) (envelope-from don@eozoon.coleman.org) Received: from eozoon.coleman.org (eozoon.coleman.org [127.0.0.1] (may be forged)) by eozoon.coleman.org (8.9.3/8.9.3) with ESMTP id PAA28094; Tue, 13 Mar 2001 15:45:37 -0800 (PST) Message-Id: <200103132345.PAA28094@eozoon.coleman.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Poul-Henning Kamp Reply-To: don@coleman.org Cc: Wilko Bulte , Chris Dillon , scsi@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Your message of "Tue, 13 Mar 2001 22:49:13 +0100." <10844.984520153@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Mar 2001 15:45:37 -0800 From: Don Coleman Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The original legato prestoserve board (VME bus) was manufactured by Micro Memory Inc, 9540 Vassar Ave Chatsworth, CA 91311 818-998-0070 Our contact was Mose' Jadon. The address and phone # are circa 1989. Amazingly enough, a web search turns up http://www.micromemory.com, and the old phone # is still valid. The original board was called the MM6704c by Micro Memory. A design firm we didn't pick wanted a bit under $100,000 for a custom engineering design, plus about $1000 per board. A PCI board is *much* smaller then a 9U VME board, and I'd expect the boards to be a lot cheaper. I think you'd want at least a couple weeks of backup, since if the machine crashes due to a hardware failure, it may not come back up soon, and the NVRAM is logically part of the disks... The original Preserve had 3 NiCd batteries to backup its low power static CMOS memory, good for about 6 months with no power (it also had a built in charger). don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 16: 0:42 2001 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 100CF37B719 for ; Tue, 13 Mar 2001 16:00:40 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA91420 for scsi@FreeBSD.org; Tue, 13 Mar 2001 17:00:39 -0700 (MST) (envelope-from ken) Date: Tue, 13 Mar 2001 17:00:39 -0700 From: "Kenneth D. Merry" To: scsi@FreeBSD.org Subject: CAM error recovery patches available Message-ID: <20010313170039.A91337@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The long-awaited rewrite of the CAM error recovery code is pretty close to completion. Diffs are here: http://people.FreeBSD.org/~ken/cam.error_recovery_diffs.20010313.context Justin did most of the work over a year ago, I have cleaned things up and added a few things. Feedback would be appreciated. It works for me, but having a wider test of it before it goes into -current would be nice. These diffs also include the beginnings of a new inteface for transfer rate negotiation in the transport layer. It isn't yet complete, though. HBA driver authors may want to take a look through that code and the code marked with AHC_NEW_TRAN_SETTINGS in the ahc driver. (That part of it is already in the tree.) 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 Tue Mar 13 18:27:35 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B61BE37B718; Tue, 13 Mar 2001 18:27:28 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA10845; Tue, 13 Mar 2001 18:25:58 -0800 Date: Tue, 13 Mar 2001 18:25:55 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Don Coleman Cc: Poul-Henning Kamp , Wilko Bulte , Chris Dillon , scsi@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103132345.PAA28094@eozoon.coleman.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yeah, he's still around. On Tue, 13 Mar 2001, Don Coleman wrote: > > The original legato prestoserve board (VME bus) was manufactured by > > Micro Memory Inc, > 9540 Vassar Ave > Chatsworth, CA 91311 > 818-998-0070 > > Our contact was Mose' Jadon. The address and phone # are circa 1989. > > Amazingly enough, a web search turns up http://www.micromemory.com, > and the old phone # is still valid. > > The original board was called the MM6704c by Micro Memory. > > A design firm we didn't pick wanted a bit under $100,000 for > a custom engineering design, plus about $1000 per board. > > A PCI board is *much* smaller then a 9U VME board, and I'd > expect the boards to be a lot cheaper. > > I think you'd want at least a couple weeks of backup, since if the > machine crashes due to a hardware failure, it may not come back > up soon, and the NVRAM is logically part of the disks... > > The original Preserve had 3 NiCd batteries to backup its low power > static CMOS memory, good for about 6 months with no power (it also > had a built in charger). > > don > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 21:55:40 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp10.phx.gblx.net (smtp10.phx.gblx.net [206.165.6.140]) by hub.freebsd.org (Postfix) with ESMTP id F129837B71A; Tue, 13 Mar 2001 21:55:35 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp10.phx.gblx.net (8.9.3/8.9.3) id WAA81114; Tue, 13 Mar 2001 22:55:19 -0700 Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp10.phx.gblx.net, id smtpd344mya; Tue Mar 13 22:55:13 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id WAA04683; Tue, 13 Mar 2001 22:55:21 -0700 (MST) From: Terry Lambert Message-Id: <200103140555.WAA04683@usr05.primenet.com> Subject: Re: Disk I/O problem in 4.3-BETA To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 14 Mar 2001 05:55:21 +0000 (GMT) Cc: Stephen.Byan@quantum.com (Stephen Byan), bright@wintelcom.net ('Alfred Perlstein'), mjacob@feral.com (Matthew Jacob), gibbs@scsiguy.com (Justin T. Gibbs), sos@freebsd.dk (Soren Schmidt), oberman@es.net (Kevin Oberman), scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG In-Reply-To: <8821.984501490@critter> from "Poul-Henning Kamp" at Mar 13, 2001 05:38:10 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >If NT and FreeBSD both support hinting of metadata writes, it's only a > >matter of time before the hardware support appears. > > I have been looking for a long time for a PCI NVRAM card at a reasonable > cost, anyone know of any with a reasonable price ? How much NVRAM do you need? It seems to me that you can get a PCI card to plug a PC-CARD into the back of a regular PC at Fry's for pretty cheap, and that there is no lack of memory cards in the PC-CARD/PCMCIA form factor. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 21:57: 1 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.136]) by hub.freebsd.org (Postfix) with ESMTP id 86EF937B719; Tue, 13 Mar 2001 21:56:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.9.3/8.9.3) with ESMTP id GAA57433; Wed, 14 Mar 2001 06:56:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f2E5vAp16089; Wed, 14 Mar 2001 06:57:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Terry Lambert Cc: Stephen.Byan@quantum.com (Stephen Byan), bright@wintelcom.net ('Alfred Perlstein'), mjacob@feral.com (Matthew Jacob), gibbs@scsiguy.com (Justin T. Gibbs), sos@freebsd.dk (Soren Schmidt), oberman@es.net (Kevin Oberman), scsi@FreeBSD.ORG, fs@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Wed, 14 Mar 2001 05:55:21 GMT." <200103140555.WAA04683@usr05.primenet.com> Date: Wed, 14 Mar 2001 06:57:10 +0100 Message-ID: <16087.984549430@critter> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103140555.WAA04683@usr05.primenet.com>, Terry Lambert writes: >> >If NT and FreeBSD both support hinting of metadata writes, it's only a >> >matter of time before the hardware support appears. >> >> I have been looking for a long time for a PCI NVRAM card at a reasonable >> cost, anyone know of any with a reasonable price ? > >How much NVRAM do you need? > >It seems to me that you can get a PCI card to plug a PC-CARD >into the back of a regular PC at Fry's for pretty cheap, and >that there is no lack of memory cards in the PC-CARD/PCMCIA >form factor. There you run into a speed problem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 23: 5:30 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6C0D837B754 for ; Tue, 13 Mar 2001 23:05:26 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA16204; Wed, 14 Mar 2001 17:35:20 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 14 Mar 2001 17:35:19 +1030 (CST) From: "Daniel O'Connor" To: support@ConnectCom.net Subject: Fixed error from SCSI BIOS Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a 'JFYI' in case someone has a similar problem.. I have an Advansys 3940UW adapter card and when it boots, I got an error "Error: Init error 0x2". This happens when it probes for devices. I am running it on a Epox 8KTA2 motherboard (KT133 chipset) and a Athlon 1Ghz. This is running on FreeBSD 4.2. There is a Sony AIT SDX-300C UW tape drive connected to the external UW connector and a Sony CRX145S CD writer connect to the internal 50 pin Ultra connector. Both the SCSI and CDROM drives have termination. I found that it worked a whole bunch better when I turned termination off.. Now to find out why I get "panic: resource_list_alloc: resource entry is busy" when loading the USB modules after putting this card in.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 13 23:26:58 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 4BAC337B71B; Tue, 13 Mar 2001 23:26:49 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA16456; Wed, 14 Mar 2001 17:56:43 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 14 Mar 2001 17:56:43 +1030 (CST) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Subject: Advansys Weirdness (tm) Cc: freebsd-scsi@freebsd.org, gibbs@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got an Advansys 3940UW and thought I had fixed a problem with it.. In previous post to -scsi I thought I had fixed the init error problem but it still happens.. As well as that error I am getting "panic: resource_list_alloc: resource entry is busy" errors when loading KLD's :( Also, the boot probe for adw0 says that the firmware load failed, so it is not attaching. I am hypothesizing that the adw driver doesn't unlock/free something it should in this case, so when another PCI driver kld is loaded the adw is reprobed and tries to do something but bombs. The second time the adw0 line is printed, there is no line which says that the firmware load failed, but I don't know if that's because it suceeded or if it bombs before then. I will get a stack trace soon. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 14 1: 0:56 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id CF30237B718; Wed, 14 Mar 2001 01:00:48 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id TAA17937; Wed, 14 Mar 2001 19:30:46 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 14 Mar 2001 19:30:46 +1030 (CST) From: "Daniel O'Connor" To: "Daniel O'Connor" Subject: RE: Advansys Weirdness (tm) Cc: gibbs@freebsd.org, freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 14-Mar-01 Daniel O'Connor wrote: > The second time the adw0 line is printed, there is no line which says that the > firmware load failed, but I don't know if that's because it suceeded or if it > bombs > before then. > > I will get a stack trace soon. OK, well I see that the Advansys code doesn't do a bus_release_resource() when an error happens. I think that in adw_pci_attach() instead of just doing return(ENXIO), do err = ENXIO; goto bailout; [ .. ] bailout: if (regs) bus_release_resource(dev, regs_type, regs_id, regs); I will see if I can work up a proper diff :) WRT the actual problem (ie the firmware doesn't load) I am guessing the card must be faulty since it has a problem in the BIOS.. (Where it says init error 0x2) - that problem doesn't happen all the time, but most of the time. Occassionally the card actually works properly though. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 14 1:31:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id B083837B718; Wed, 14 Mar 2001 01:31:31 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id UAA18463; Wed, 14 Mar 2001 20:01:29 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 14 Mar 2001 20:01:29 +1030 (CST) From: "Daniel O'Connor" To: "Daniel O'Connor" Subject: RE: Advansys Weirdness (tm) Cc: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org, gibbs@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 14-Mar-01 Daniel O'Connor wrote: > bus_release_resource(dev, regs_type, regs_id, regs); > > I will see if I can work up a proper diff :) Well that wasn't as hard as I expected :) Attached is a diff which seems to work OK when the card firmware fails to load. (As in the next KLD load doesn't die) I think adw_attach needs a bus_teardown_intr in fail to be symmetrical, but I'm not 100% sure. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 14 1:35:43 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D151937B732; Wed, 14 Mar 2001 01:35:29 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id UAA18536; Wed, 14 Mar 2001 20:05:28 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.4.0.FreeBSD:010314200528:9706=_" In-Reply-To: Date: Wed, 14 Mar 2001 20:05:28 +1030 (CST) From: "Daniel O'Connor" To: "Daniel O'Connor" Subject: RE: Advansys Weirdness (tm) Cc: gibbs@freebsd.org, freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format --_=XFMail.1.4.0.FreeBSD:010314200528:9706=_ Content-Type: text/plain; charset=us-ascii > Attached is a diff which seems to work OK when the card firmware fails to load. > (As in the next KLD load doesn't die) Whoops.. actually attach the diff this time. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.4.0.FreeBSD:010314200528:9706=_ Content-Disposition: attachment; filename="adw_pci_release.diff" Content-Transfer-Encoding: 7bit Content-Description: adw_pci_release.diff Content-Type: text/plain; charset=us-ascii; name=adw_pci_release.diff; SizeOnDisk=1836 Index: adw_pci.c =================================================================== RCS file: /local1/ncvs/src/sys/dev/advansys/adw_pci.c,v retrieving revision 1.12.2.1 diff -u -r1.12.2.1 adw_pci.c --- adw_pci.c 2000/08/02 22:22:40 1.12.2.1 +++ adw_pci.c 2001/03/14 09:26:38 @@ -231,16 +231,18 @@ } adw = adw_alloc(dev, regs, regs_type, regs_id); - if (adw == NULL) - return(ENOMEM); - + if (adw == NULL) { + error = ENOMEM; + goto bailout; + } + /* * Now that we have access to our registers, just verify that * this really is an AdvanSys device. */ if (adw_find_signature(adw) == 0) { - adw_free(adw); - return (ENXIO); + error = ENXIO; + goto bailout; } adw_reset_chip(adw); @@ -248,7 +250,7 @@ error = entry->setup(dev, entry, adw); if (error != 0) - return (error); + goto bailout; /* Ensure busmastering is enabled */ command |= PCIM_CMD_BUSMASTEREN; @@ -272,16 +274,14 @@ if (error != 0) { printf("%s: Could not allocate DMA tag - error %d\n", adw_name(adw), error); - adw_free(adw); - return (error); + goto bailout; } adw->init_level++; error = adw_init(adw); if (error != 0) { - adw_free(adw); - return (error); + goto bailout; } /* @@ -300,13 +300,24 @@ adw->irq = bus_alloc_resource(dev, adw->irq_res_type, &zero, 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); if (adw->irq == NULL) { - adw_free(adw); - return (ENOMEM); + error = ENOMEM; + goto bailout; } error = adw_attach(adw); - if (error != 0) - adw_free(adw); + + bailout: + if (error != 0) { + if (regs) + bus_release_resource(dev, regs_type, regs_id, regs); + if (adw->irq) { + /* teardown intr? */ + bus_release_resource(dev, adw->irq_res_type, 0, adw->irq); + } + if (adw) + adw_free(adw); + } + return (error); } --_=XFMail.1.4.0.FreeBSD:010314200528:9706=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 14 15:43:11 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from gate.lustig.com (lustig.ne.mediaone.net [24.91.125.166]) by hub.freebsd.org (Postfix) with SMTP id F383637B71A for ; Wed, 14 Mar 2001 15:43:07 -0800 (PST) (envelope-from barry@lustig.com) Received: (qmail 82388 invoked from network); 14 Mar 2001 23:43:06 -0000 Received: from gate.lustig.com (HELO lustig.com) (barry@205.246.2.242) by gate.lustig.com with SMTP; 14 Mar 2001 23:43:06 -0000 Message-ID: <3AB00209.DEE27796@lustig.com> Date: Wed, 14 Mar 2001 18:43:05 -0500 From: Barry Lustig Organization: Barry Lustig & Associates, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: scsi@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA References: <10186.984516305@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Poul-Henning Kamp wrote: > > My ideal product would be a PCI card with some SRAM, and a holder > for a 9v DURACELL. > Does anyone know what NetApp uses? Their NVRAM board is PCI. barry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 15 17:31:42 2001 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 A3EDF37B719; Thu, 15 Mar 2001 17:31:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA09431; Thu, 15 Mar 2001 18:31:18 -0700 (MST) (envelope-from ken) Date: Thu, 15 Mar 2001 18:31:18 -0700 From: "Kenneth D. Merry" To: scsi@FreeBSD.org Cc: current@FreeBSD.org Subject: aic(4) driver patch Message-ID: <20010315183118.A9399@panzer.kdm.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Attached is a patch for the aic(4) driver to do the following: - enable 10MHz (fast SCSI) operation on boards that support it. (only aic6360 boards with fast SCSI enabled can do it) - bounds check sync periods and offsets passed in from the transport layer - tell the user which resource allocation failed (for the ISA probe) if we weren't able to allocate an IRQ, DRQ or I/O port. Anyway, this patch should apply and run on both -stable and -current. It works for me, but I'd appreciate feedback. Ken -- Kenneth Merry ken@kdm.org --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="aic.sync_diffs.20010315" ==== //depot/FreeBSD-adaptec/src/sys/dev/aic/aic.c#2 - /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aic.c ==== *** /tmp/tmp.77783.0 Thu Mar 15 18:25:00 2001 --- /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aic.c Thu Mar 15 18:03:03 2001 *************** *** 196,211 **** if ((cts->valid & CCB_TRANS_SYNC_RATE_VALID) != 0) { ti->goal.period = cts->sync_period; ! if (ti->goal.period != ti->current.period) ! ti->flags |= TINFO_SDTR_NEGO; } if ((cts->valid & CCB_TRANS_SYNC_OFFSET_VALID) != 0) { ti->goal.offset = cts->sync_offset; ! if (ti->goal.offset != ti->current.offset) ! ti->flags |= TINFO_SDTR_NEGO; } splx(s); ccb->ccb_h.status = CAM_REQ_CMP; xpt_done(ccb); --- 196,221 ---- if ((cts->valid & CCB_TRANS_SYNC_RATE_VALID) != 0) { ti->goal.period = cts->sync_period; ! ! if (ti->goal.period > aic->min_period) { ! ti->goal.period = 0; ! ti->goal.offset = 0; ! } else if (ti->goal.period < aic->max_period) ! ti->goal.period = aic->max_period; } if ((cts->valid & CCB_TRANS_SYNC_OFFSET_VALID) != 0) { ti->goal.offset = cts->sync_offset; ! if (ti->goal.offset == 0) ! ti->goal.period = 0; ! else if (ti->goal.offset > AIC_SYNC_OFFSET) ! ti->goal.offset = AIC_SYNC_OFFSET; } + if ((ti->goal.period != ti->current.period) + || (ti->goal.offset != ti->current.offset)) + ti->flags |= TINFO_SDTR_NEGO; + splx(s); ccb->ccb_h.status = CAM_REQ_CMP; xpt_done(ccb); *************** *** 1427,1435 **** aic->flags |= AIC_DISC_ENABLE; if (PORTB_DMA(portb)) aic->flags |= AIC_DMA_ENABLE; ! if (aic_inb(aic, REV)) aic->flags |= AIC_DWIO_ENABLE; free_scbs = NULL; for (i = 255; i >= 0; i--) { scb = &aic->scbs[i]; --- 1437,1461 ---- aic->flags |= AIC_DISC_ENABLE; if (PORTB_DMA(portb)) aic->flags |= AIC_DMA_ENABLE; ! ! /* ! * We can do fast SCSI (10MHz clock rate) if bit 4 of portb ! * is set and we've got a 6360. The 6260 can only do standard ! * 5MHz SCSI. ! */ ! if (aic_inb(aic, REV)) { ! if (PORTB_FSYNC(portb)) { ! aic->max_period = AIC_FAST_SYNC_PERIOD; ! aic->flags |= AIC_FAST_ENABLE; ! } else ! aic->max_period = AIC_SYNC_PERIOD; ! aic->flags |= AIC_DWIO_ENABLE; + } else + aic->max_period = AIC_SYNC_PERIOD; + aic->min_period = AIC_MIN_SYNC_PERIOD; + free_scbs = NULL; for (i = 255; i >= 0; i--) { scb = &aic->scbs[i]; *************** *** 1445,1451 **** ti->flags = TINFO_TAG_ENB; if (aic->flags & AIC_DISC_ENABLE) ti->flags |= TINFO_DISC_ENB; ! ti->user.period = AIC_SYNC_PERIOD; ti->user.offset = AIC_SYNC_OFFSET; ti->scsirate = 0; } --- 1471,1477 ---- ti->flags = TINFO_TAG_ENB; if (aic->flags & AIC_DISC_ENABLE) ti->flags |= TINFO_DISC_ENB; ! ti->user.period = aic->max_period; ti->user.offset = AIC_SYNC_OFFSET; ti->scsirate = 0; } *************** *** 1513,1518 **** --- 1539,1546 ---- printf(", disconnection"); if (aic->flags & AIC_PARITY_ENABLE) printf(", parity check"); + if (aic->flags & AIC_FAST_ENABLE) + printf(", fast SCSI"); printf("\n"); aic_cam_rescan(aic); /* have CAM rescan the bus */ ==== //depot/FreeBSD-adaptec/src/sys/dev/aic/aic6360reg.h#1 - /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aic6360reg.h ==== *** /tmp/tmp.77783.1 Thu Mar 15 18:25:00 2001 --- /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aic6360reg.h Mon Mar 12 18:31:29 2001 *************** *** 320,327 **** --- 320,329 ---- #define PORTA_PARITY(a) ((a) & 0x80) /* PORTB */ + #define PORTB_EXTTRAN(b)((b) & 1) #define PORTB_DISC(b) ((b) & 4) #define PORTB_SYNC(b) ((b) & 8) + #define PORTB_FSYNC(b) ((b) & 0x10) #define PORTB_BOOT(b) ((b) & 0x40) #define PORTB_DMA(b) ((b) & 0x80) ==== //depot/FreeBSD-adaptec/src/sys/dev/aic/aic_isa.c#2 - /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aic_isa.c ==== *** /tmp/tmp.77783.2 Thu Mar 15 18:25:00 2001 --- /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aic_isa.c Thu Mar 15 18:20:27 2001 *************** *** 68,81 **** rid = 0; sc->sc_port = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0ul, ~0ul, AIC_ISA_PORTSIZE, RF_ACTIVE); ! if (!sc->sc_port) return (ENOMEM); if (isa_get_irq(dev) != -1) { rid = 0; sc->sc_irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0ul, ~0ul, 1, RF_ACTIVE); if (!sc->sc_irq) { aic_isa_release_resources(dev); return (ENOMEM); } --- 68,84 ---- rid = 0; sc->sc_port = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0ul, ~0ul, AIC_ISA_PORTSIZE, RF_ACTIVE); ! if (!sc->sc_port) { ! device_printf(dev, "I/O port allocation failed\n"); return (ENOMEM); + } if (isa_get_irq(dev) != -1) { rid = 0; sc->sc_irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0ul, ~0ul, 1, RF_ACTIVE); if (!sc->sc_irq) { + device_printf(dev, "IRQ allocation failed\n"); aic_isa_release_resources(dev); return (ENOMEM); } *************** *** 86,91 **** --- 89,95 ---- sc->sc_drq = bus_alloc_resource(dev, SYS_RES_DRQ, &rid, 0ul, ~0ul, 1, RF_ACTIVE); if (!sc->sc_drq) { + device_printf(dev, "DRQ allocation failed\n"); aic_isa_release_resources(dev); return (ENOMEM); } ==== //depot/FreeBSD-adaptec/src/sys/dev/aic/aicvar.h#1 - /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aicvar.h ==== *** /tmp/tmp.77783.3 Thu Mar 15 18:25:00 2001 --- /a/ken/perforce/FreeBSD-adaptec/src/sys/dev/aic/aicvar.h Thu Mar 15 17:52:12 2001 *************** *** 91,96 **** --- 91,99 ---- struct aic_tinfo tinfo[8]; struct aic_scb scbs[256]; + + int min_period; + int max_period; }; #define AIC_DISC_ENABLE 0x01 *************** *** 100,105 **** --- 103,109 ---- #define AIC_RESOURCE_SHORTAGE 0x10 #define AIC_DROP_MSGIN 0x20 #define AIC_BUSFREE_OK 0x40 + #define AIC_FAST_ENABLE 0x80 #define AIC_IDLE 0x00 #define AIC_SELECTING 0x01 *************** *** 114,119 **** --- 118,125 ---- #define AIC_MSG_MSGBUF 0x80 #define AIC_SYNC_PERIOD (200 / 4) + #define AIC_FAST_SYNC_PERIOD (100 / 4) + #define AIC_MIN_SYNC_PERIOD 112 #define AIC_SYNC_OFFSET 8 #define aic_inb(aic, port) \ --XsQoSWH+UP9D9v3l-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 16 14:37:24 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from femail1.rdc1.on.home.com (femail1.rdc1.on.home.com [24.2.9.88]) by hub.freebsd.org (Postfix) with ESMTP id 73A2137B718; Fri, 16 Mar 2001 14:37:19 -0800 (PST) (envelope-from james@ehlo.com) Received: from cr237535-a.bloor1.on.wave.home.com ([24.157.24.3]) by femail1.rdc1.on.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010316223555.RQKH18593.femail1.rdc1.on.home.com@cr237535-a.bloor1.on.wave.home.com>; Fri, 16 Mar 2001 14:35:55 -0800 Received: from james by cr237535-a.bloor1.on.wave.home.com with local (Exim 3.15 #1) id 14e2qS-0003e3-00; Fri, 16 Mar 2001 17:37:16 -0500 Date: Fri, 16 Mar 2001 17:37:16 -0500 From: James FitzGibbon To: current@freebsd.org Cc: scsi@freebsd.org Subject: Mylex eXtremeRAID 2000 timeout/hang Message-ID: <20010316173716.E11769@ehlo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are trying to install a Mylex eXtreme 2000 card with a Dell Powervault 12 drive SCA housing. The drives in the array are numbered 0-5 and 8-13. The backplane of the array is id 15. During the kernel probe, we see the message mly0: drive at 03:15 not responding five times after the "waiting 15 seconds for SCSI devices to spin up" message, and then nothing else. The system doesn't hang, but it never goes anywhere from there. This is with F/W 6.00-00 and BIOS 6.00-01. Any ideas ? -- j. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 16 15:52:39 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id BB3C237B718; Fri, 16 Mar 2001 15:52:34 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id RAA28052; Fri, 16 Mar 2001 17:52:32 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 16 Mar 2001 17:52:32 -0600 (CST) From: Chris Dillon To: James FitzGibbon Cc: , Subject: Re: Mylex eXtremeRAID 2000 timeout/hang In-Reply-To: <20010316173716.E11769@ehlo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 16 Mar 2001, James FitzGibbon wrote: > We are trying to install a Mylex eXtreme 2000 card with a Dell > Powervault 12 drive SCA housing. The drives in the array are > numbered 0-5 and 8-13. The backplane of the array is id 15. > > During the kernel probe, we see the message > > mly0: drive at 03:15 not responding > > five times after the "waiting 15 seconds for SCSI devices to spin > up" message, and then nothing else. The system doesn't hang, but > it never goes anywhere from there. This is with F/W 6.00-00 and > BIOS 6.00-01. How long did you wait? I have a similar problem with an AcceleRAID 170 in -STABLE where I have to wait several minutes before it finally gets around to booting. I get the following, with about 30 to 40 seconds in between each "error": Waiting 7 seconds for SCSI devices to settle mly0: physical device 0:6 sense data received mly0: sense key 5 asc 00 ascq 00 mly0: info 00000000 csi 00000000 mly0: physical device 0:6 sense data received mly0: sense key 5 asc 00 ascq 00 mly0: info 00000000 csi 00000000 mly0: physical device 0:6 sense data received mly0: sense key 5 asc 00 ascq 00 mly0: info 00000000 csi 00000000 mly0: physical device 0:6 sense data received mly0: sense key 5 asc 00 ascq 00 mly0: info 00000000 csi 00000000 mly0: physical device 0:6 sense data received mly0: sense key 5 asc 00 ascq 00 mly0: info 00000000 csi 00000000 da0 at mly0 bus 1 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 17480MB (35799040 512 byte sectors: 255H 63S/T 2228C) Mounting root from ufs:/dev/da0s1a Device 0:6:0 is the enclosure management device (the "backplane", I guess) in the SuperMicro SuperServer 6040, which I think is available separately as their CSE-031 drive enclosure. IIRC, the actual enclosure management device is the QLogic GEM. I also had a problem after a recent upgrade to 4.3-BETA where if I left my extra drive in the chassis, I would get the following error just before the 0:6:0 errors: (probe32:mly0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe32:mly0:0:2:0): error code 0 Device 0:2:0 was a spare drive (not configured as a hot spare, IIRC, just sitting there completely unconfigured, waiting for me to do something with it, or sacrifice itself as a warm spare if another drive died). After waiting for the previously mentioned device 0:6:0 errors to go by, the system would panic immediately afterwards: Fatal trap 18: integer divide fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 instruction pointer = 0x8:0xc01477f1 stack pointer = 0x10:0xff806e04 frame pointer = 0x10:0xff806e1c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = <- SMP: XXX trap number = 18 panic: integer divide fault mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 syncing disks... done Uptime: 4m23s mly0: flushing cache...done On a hunch I removed the unconfigured disk from the drive enclosure and the system booted just fine... Mike? :-) P.S.: I'm getting stuff in my dmesg buffer from _previous_ boots... I've never seen a system do that. That's how I could cut/paste that panic. :-) Is that a bug, or a feature? Its a nice feature (which my other 4.2-STABLE boxes don't seem to have). Some of the information seems to get corrupted (mixed-up might be a better explanation) around the time of a panic, for example: [...snip...] mly0: physical device 0:6 sense data received mly0: secuous mode disabled Fatal trap 18: integer divide fault while in kernel mode [...snip...] All new dmesg info is just fine, of course, and all "normal" reboot sequences (without a powerdown) seem to preserve the old dmesg info perfectly. Too bad more of my boxes don't exhibit this feature. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 17 14:39:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 3BA0837B71A; Sat, 17 Mar 2001 14:39:27 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 14ePHq-0001VY-00; Sat, 17 Mar 2001 14:35:03 -0800 Date: Sat, 17 Mar 2001 14:34:46 -0800 (PST) From: Tom Samplonius To: Chris Dillon Cc: James FitzGibbon , scsi@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Mylex eXtremeRAID 2000 timeout/hang In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 16 Mar 2001, Chris Dillon wrote: ... > I also had a problem after a recent upgrade to 4.3-BETA where if I > left my extra drive in the chassis, I would get the following error > just before the 0:6:0 errors: The mly driver has been updated a short while ago. I've recently discovered some issues as well. I can hang the disks under heavy IO with a Mylex 352 card. ... > P.S.: I'm getting stuff in my dmesg buffer from _previous_ boots... > I've never seen a system do that. That's how I could cut/paste that > panic. :-) Is that a bug, or a feature? Its a nice feature (which my > other 4.2-STABLE boxes don't seem to have). Some of the information Been around for a long time. As long as your hardware preserved the memory state during a warm boot, the previous dmesg can be found by the kernel. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 17 15:18:53 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id ED0A237B718; Sat, 17 Mar 2001 15:18:51 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2HNJpU02465; Sat, 17 Mar 2001 15:19:52 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103172319.f2HNJpU02465@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Samplonius Cc: Chris Dillon , James FitzGibbon , scsi@FreeBSD.ORG Subject: Re: Mylex eXtremeRAID 2000 timeout/hang In-reply-to: Your message of "Sat, 17 Mar 2001 14:34:46 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 17 Mar 2001 15:19:51 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Fri, 16 Mar 2001, Chris Dillon wrote: > > ... > > I also had a problem after a recent upgrade to 4.3-BETA where if I > > left my extra drive in the chassis, I would get the following error > > just before the 0:6:0 errors: > > The mly driver has been updated a short while ago. > > I've recently discovered some issues as well. I can hang the disks > under heavy IO with a Mylex 352 card. Got another bug report yet? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 17 17:29:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 3774337B71D; Sat, 17 Mar 2001 17:29:35 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id TAA47820; Sat, 17 Mar 2001 19:29:27 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 17 Mar 2001 19:29:27 -0600 (CST) From: Chris Dillon To: Tom Samplonius Cc: James FitzGibbon , , Subject: Re: Mylex eXtremeRAID 2000 timeout/hang In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 17 Mar 2001, Tom Samplonius wrote: > > P.S.: I'm getting stuff in my dmesg buffer from _previous_ boots... > > I've never seen a system do that. That's how I could cut/paste that > > panic. :-) Is that a bug, or a feature? Its a nice feature (which my > > other 4.2-STABLE boxes don't seem to have). Some of the information > > Been around for a long time. As long as your hardware preserved > the memory state during a warm boot, the previous dmesg can be > found by the kernel. Interesting. I knew that would have to be a requirement, but I figured I would have had more than one system that did it. The one that does it happens to be a SuperMicro system with the ServerWorks III HE-SL chipset. I assume this is a function of the BIOS and not the chipset, since I have a Compaq server with the ServerWorks III LE chipset and it apparently clears memory on reboot. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message