From owner-freebsd-scsi@FreeBSD.ORG Mon Jul 21 07:21:51 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A46C637B401 for ; Mon, 21 Jul 2003 07:21:51 -0700 (PDT) Received: from acs.sk (acs.sk [62.176.161.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3059743FA3 for ; Mon, 21 Jul 2003 07:21:50 -0700 (PDT) (envelope-from tomas@hodan.sk) Received: from dlth (unused [66.187.227.249] (may be forged)) (authenticated bits=0) by acs.sk (8.12.9/8.12.9) with ESMTP id h6LELiQT099975 for ; Mon, 21 Jul 2003 16:21:47 +0200 (CEST) (envelope-from tomas@hodan.sk) From: "Tomas Hodan" To: Date: Mon, 21 Jul 2003 15:21:43 +0100 Message-ID: <000801c34f93$6ab046b0$9f001fac@emea.ads.autodesk.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) Subject: ql2200 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 14:21:52 -0000 I found funny think, with enabled bios it works, please could someone sendme example of the qlogic board settings? thx tomas From owner-freebsd-scsi@FreeBSD.ORG Mon Jul 21 11:02:48 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B29C537B40C for ; Mon, 21 Jul 2003 11:02:48 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B48C543FBD for ; Mon, 21 Jul 2003 11:02:47 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6LI2lUp059205 for ; Mon, 21 Jul 2003 11:02:47 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6LI2ltR059199 for scsi@freebsd.org; Mon, 21 Jul 2003 11:02:47 -0700 (PDT) Date: Mon, 21 Jul 2003 11:02:47 -0700 (PDT) Message-Id: <200307211802.h6LI2ltR059199@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 18:02:49 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jul 21 14:37:13 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC36737B40F for ; Mon, 21 Jul 2003 14:37:13 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F1F243F3F for ; Mon, 21 Jul 2003 14:37:13 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6LLbDUp005484 for ; Mon, 21 Jul 2003 14:37:13 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6LLbCOP005478 for scsi@freebsd.org; Mon, 21 Jul 2003 14:37:12 -0700 (PDT) Date: Mon, 21 Jul 2003 14:37:12 -0700 (PDT) Message-Id: <200307212137.h6LLbCOP005478@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 21:37:14 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jul 21 14:47:34 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0483E37B408 for ; Mon, 21 Jul 2003 14:47:34 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B9D743FE9 for ; Mon, 21 Jul 2003 14:47:31 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6LLlUUp010529 for ; Mon, 21 Jul 2003 14:47:30 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6LLlT6K010523 for scsi@freebsd.org; Mon, 21 Jul 2003 14:47:29 -0700 (PDT) Date: Mon, 21 Jul 2003 14:47:29 -0700 (PDT) Message-Id: <200307212147.h6LLlT6K010523@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 21:47:34 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. From owner-freebsd-scsi@FreeBSD.ORG Tue Jul 22 13:42:47 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F59A37B401; Tue, 22 Jul 2003 13:42:47 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1AC443F85; Tue, 22 Jul 2003 13:42:46 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([12.233.125.100]) by attbi.com (rwcrmhc12) with ESMTP id <2003072220424401400ana18e>; Tue, 22 Jul 2003 20:42:44 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA51674; Tue, 22 Jul 2003 13:42:43 -0700 (PDT) Date: Tue, 22 Jul 2003 13:42:41 -0700 (PDT) From: Julian Elischer To: scsi@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: scsi/mylex coredumps.. X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 20:42:47 -0000 I have the following dmesg snippet from a 4.x system [...] > Jul 16 17:39:55 oos0b /kernel: /raid3: bad dir ino 3 at offset 0: > mangled entry > Jul 16 17:39:55 oos0b /kernel: panic: ufs_dirbad: bad dir > Jul 16 17:39:55 oos0b /kernel: > Jul 16 17:39:55 oos0b /kernel: syncing disks... 49 13 1 1 1 1 1 1 1 1 > 1 1 1 1 1 1 1 1 1 1 1 1 > Jul 16 17:39:55 oos0b /kernel: giving up on 1 buffers > Jul 16 17:39:55 oos0b /kernel: Uptime: 94d11h5m4s > Jul 16 17:39:55 oos0b /kernel: mly0: flushing cache...done > Jul 16 17:39:55 oos0b /kernel: > Jul 16 17:39:55 oos0b /kernel: dumping to dev #da/0x20001, offset > 999584 > Jul 16 17:39:55 oos0b /kernel: dump 511 510 509 508 507 506 505 504 > 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 > 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 > 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 > 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 > 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 > 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 > 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 > 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 > 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 > 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 > 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 > 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 > 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 > 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 > 272 271 270 269 268 267 266 265 264 263 262 261 260 25 > Jul 16 17:39:55 oos0b /kernel: 7 256 255 254 253 252 251 250 249 248 > 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 > 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 > 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 > 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 > 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 > 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 > 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 > 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 > 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 > 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 > 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 > 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 > 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 > 11 10 9 8 7 6 5 4 3 2 1 0 > > yet there is no core-dump on the drive. Is there something that needs to be added to the Mylex mly driver to allow core-dumps to actually be written? obviously the top level thinks it is writing a core-dump.. While I'm at it, scottl added a bugfix in 5.x (1.20) that he stated was also present in 4.x. Any change that this might be MFC'd? julian From owner-freebsd-scsi@FreeBSD.ORG Tue Jul 22 14:22:43 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2074437B401; Tue, 22 Jul 2003 14:22:43 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5240743FBF; Tue, 22 Jul 2003 14:22:42 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h6MLMfo11810; Tue, 22 Jul 2003 14:22:41 -0700 Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id OAA10469; Tue, 22 Jul 2003 14:22:41 -0700 (PDT) Date: Tue, 22 Jul 2003 15:24:22 -0600 From: "Justin T. Gibbs" To: Don Lewis , ray.taft@jupiterhosting.com Message-ID: <625822704.1058909061@aslan.btc.adaptec.com> In-Reply-To: <200307150209.h6F29mM7028468@gw.catspoiler.org> References: <200307150209.h6F29mM7028468@gw.catspoiler.org> X-Mailer: Mulberry/3.1.0b3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 2120S Errors X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 21:22:43 -0000 > Under extreme load one of my Seagate SCSI drives will defer some > commands "forever", until CAM times out the command and resets the drive > and/or the SCSI bus. CAM issues a periodic ordered tag to avoid this problem. This should work on any drive that honors the ordered tag attribute. -- Justin From owner-freebsd-scsi@FreeBSD.ORG Tue Jul 22 14:51:09 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 814EA37B401 for ; Tue, 22 Jul 2003 14:51:09 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id C386F43FA3 for ; Tue, 22 Jul 2003 14:51:08 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h6MLp8o21220; Tue, 22 Jul 2003 14:51:08 -0700 Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id OAA26707; Tue, 22 Jul 2003 14:51:07 -0700 (PDT) Date: Tue, 22 Jul 2003 15:52:47 -0600 From: "Justin T. Gibbs" To: Felix Deichmann , Nate Lawson Message-ID: <645732704.1058910767@aslan.btc.adaptec.com> In-Reply-To: <3F0F03CB.9040306@web.de> References: <200307111732.h6BHWHd3074973@siralan.org> <3F0EF9A8.10403@fdei.de> <20030711112645.B8411@root.org> <3F0F03CB.9040306@web.de> X-Mailer: Mulberry/3.1.0b3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: FreeBSD SCSI Subject: Re: SCB trouble on SMP machine with AHC X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 21:51:09 -0000 > BTW, I have now updated the firmware of the SCSI disks (Quantum Capella) > to the lastest version I could find on the net. No change whatsoever. As Scott Long mentioned, FreeBSD is not routing interrupts correctly for you while in SMP mode. I forget who is the current expert in this area, but it is probably John Baldwin. You might want to contact him about what kinds of debugging information he needs in order to better understand why interrupts are not being routed correctly on your system. -- Justin From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 01:45:12 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D722A37B401 for ; Wed, 23 Jul 2003 01:45:12 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 042F343FA3 for ; Wed, 23 Jul 2003 01:45:12 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.20) id 19fFFG-0009d7-3v for freebsd-scsi@FreeBSD.org; Wed, 23 Jul 2003 10:45:10 +0200 Date: Wed, 23 Jul 2003 10:45:10 +0200 From: Sheldon Hearn To: freebsd-scsi@FreeBSD.org Message-ID: <20030723084510.GC32528@starjuice.net> Mail-Followup-To: freebsd-scsi@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn Subject: Can Adaptec AIC-7902 do RAID-5? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 08:45:13 -0000 Hi folks, I've been googling like crazy and have gotten mixed answers on the AIC-7902's RAID support. The product spec says it can do RAID-0 and RAID-1. Other articles show benchmarks involving RAID-5. I'm concerned that this is software RAID-5, which won't do me any good at all for FreeBSD. Any FreeBSD users using an AIC-7902 with 3 or more disks in a RAID-5 configuration? Thanks, Sheldon. From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 04:27:12 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E01E937B401 for ; Wed, 23 Jul 2003 04:27:12 -0700 (PDT) Received: from c210-49-151-50.thorn1.nsw.optusnet.com.au (c210-49-151-50.thorn1.nsw.optusnet.com.au [210.49.151.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D97CD43F93 for ; Wed, 23 Jul 2003 04:27:11 -0700 (PDT) (envelope-from tonymaher@optushome.com.au) Received: from dt.home (localhost [127.0.0.1])ESMTP id h6NBPnx2038339 for ; Wed, 23 Jul 2003 21:25:49 +1000 (EST) (envelope-from tonym@dt.home) Received: (from tonym@localhost) by dt.home (8.12.9/8.12.9/Submit) id h6NBPiIS038040 for scsi@freebsd.org; Wed, 23 Jul 2003 21:25:44 +1000 (EST) (envelope-from tonym) Date: Wed, 23 Jul 2003 21:25:44 +1000 (EST) From: Tony Maher Message-Id: <200307231125.h6NBPiIS038040@dt.home> To: scsi@freebsd.org Subject: probing LUN's X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 11:27:13 -0000 Hello, I have been attempting to get a Hitachi SAN attached to a FreeBSD box via a Qlogic 2300 card. The card appeared to work ok (as evidenced by verbose boot messages but no disk(s) was seen. Finally was able to see disk with a 'camcontrol rescan 1:0:4' command. Previous 'camcontrol rescan all' and 'camcontrol rescan 1' failed to see disk. (and obviously not seen at boot time). I did not set the SAN up but from a cursory examination: The SAN has two controllers and two 'logical' raid 5 devices. One controller is connected to a Sun box which sees c1t0d[0-3] and the 4th lun appears to be given over to the second controller for the FreeBSD box. I assume this means that CAM does not probe all LUN's if no device at LUN 0 or sys/cam/cam_xpt.c has quirk entry for device that disables LUN probing. There is quirk for {"HITACHI", "DK31*"} but the SAN reports as Hitachi DF600F (I think, sorry its at work and I cannot access it currently) so the second case shouldn't be a problem. Am I reading this correctly? thanks -- tonym From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 05:25:27 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D79C637B401 for ; Wed, 23 Jul 2003 05:25:27 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF0FA43F93 for ; Wed, 23 Jul 2003 05:25:26 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h6NCPQYU051688 for ; Wed, 23 Jul 2003 06:25:26 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h6NCPQZ9051687 for freebsd-scsi@FreeBSD.org; Wed, 23 Jul 2003 06:25:26 -0600 (MDT) (envelope-from ken) Date: Wed, 23 Jul 2003 06:25:25 -0600 From: "Kenneth D. Merry" To: freebsd-scsi@FreeBSD.org Message-ID: <20030723122525.GA51640@panzer.kdm.org> References: <20030723084510.GC32528@starjuice.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723084510.GC32528@starjuice.net> User-Agent: Mutt/1.4.1i Subject: Re: Can Adaptec AIC-7902 do RAID-5? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 12:25:28 -0000 On Wed, Jul 23, 2003 at 10:45:10 +0200, Sheldon Hearn wrote: > Hi folks, > > I've been googling like crazy and have gotten mixed answers on the > AIC-7902's RAID support. > > The product spec says it can do RAID-0 and RAID-1. Other articles show > benchmarks involving RAID-5. I'm concerned that this is software > RAID-5, which won't do me any good at all for FreeBSD. > > Any FreeBSD users using an AIC-7902 with 3 or more disks in a RAID-5 > configuration? The RAID-0 and RAID-1 support (and RAID-10) is done in software. The BIOS on the -R cards understands RAID metadata and can boot from a RAID array. After that, you need support for Adaptec RAID metadata from your OS software RAID stack. If you've seen RAID-5 numbers, they were from a software RAID stack. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 05:59:33 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8A6237B401 for ; Wed, 23 Jul 2003 05:59:33 -0700 (PDT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96B1343F85 for ; Wed, 23 Jul 2003 05:59:32 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.mj.niksun.com (stiegl.mj.niksun.com [10.70.0.231]) h6NCwZlT019129; Wed, 23 Jul 2003 08:58:35 -0400 (EDT) (envelope-from ath@stiegl.mj.niksun.com) X-RAV-AntiVirus: This e-mail has been scanned for viruses. Received: from stiegl.mj.niksun.com (localhost.niksun.com [127.0.0.1]) h6NCwZm8042540; Wed, 23 Jul 2003 08:58:35 -0400 (EDT) (envelope-from ath@stiegl.mj.niksun.com) Received: (from ath@localhost) by stiegl.mj.niksun.com (8.12.6p2/8.12.6/Submit) id h6NCwZK1042539; Wed, 23 Jul 2003 08:58:35 -0400 (EDT) To: Tony Maher References: <200307231125.h6NBPiIS038040@dt.home> From: Andrew Heybey Date: 23 Jul 2003 08:58:34 -0400 In-Reply-To: <200307231125.h6NBPiIS038040@dt.home> Message-ID: <85vfttl7r9.fsf@stiegl.mj.niksun.com> Lines: 29 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: scsi@freebsd.org Subject: Re: probing LUN's X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 12:59:34 -0000 >>On Wed, 23 Jul 2003 21:25:44 +1000 (EST), Tony Maher said: tonymaher> Hello, I have been attempting to get a Hitachi SAN tonymaher> attached to a FreeBSD box via a Qlogic 2300 card. The tonymaher> card appeared to work ok (as evidenced by verbose boot tonymaher> messages but no disk(s) was seen. Finally was able to tonymaher> see disk with a 'camcontrol rescan 1:0:4' tonymaher> command. Previous 'camcontrol rescan all' and 'camcontrol tonymaher> rescan 1' failed to see disk. (and obviously not seen at tonymaher> boot time). tonymaher> I did not set the SAN up but from a cursory examination: tonymaher> The SAN has two controllers and two 'logical' raid 5 tonymaher> devices. One controller is connected to a Sun box which tonymaher> sees c1t0d[0-3] and the 4th lun appears to be given over tonymaher> to the second controller for the FreeBSD box. tonymaher> I assume this means that CAM does not probe all LUN's if tonymaher> no device at LUN 0 or sys/cam/cam_xpt.c has quirk entry tonymaher> for device that disables LUN probing. There is quirk for tonymaher> {"HITACHI", "DK31*"} but the SAN reports as Hitachi tonymaher> DF600F (I think, sorry its at work and I cannot access it tonymaher> currently) so the second case shouldn't be a problem. You need the ispfw driver (either compiled-in or modloaded) to probe luns beyond LUN 0 for the QLogic FC card. If that is not your problem, then I do not know... andrew From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 08:05:53 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1C6F37B401 for ; Wed, 23 Jul 2003 08:05:53 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id CA4CE43F75 for ; Wed, 23 Jul 2003 08:05:52 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 6608 invoked by uid 1002); 23 Jul 2003 15:05:51 -0000 Received: from adsl-64-58-12-196.mho.net (HELO freebsd.org) (64.58.12.196) by smtp.mho.net with SMTP; 23 Jul 2003 15:05:51 -0000 Message-ID: <3F1EA458.3020106@freebsd.org> Date: Wed, 23 Jul 2003 09:06:00 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sheldon Hearn References: <20030723084510.GC32528@starjuice.net> In-Reply-To: <20030723084510.GC32528@starjuice.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: Can Adaptec AIC-7902 do RAID-5? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 15:05:54 -0000 Sheldon Hearn wrote: > Hi folks, > > I've been googling like crazy and have gotten mixed answers on the > AIC-7902's RAID support. > > The product spec says it can do RAID-0 and RAID-1. Other articles show > benchmarks involving RAID-5. I'm concerned that this is software > RAID-5, which won't do me any good at all for FreeBSD. > > Any FreeBSD users using an AIC-7902 with 3 or more disks in a RAID-5 > configuration? > > Thanks, > Sheldon. A 7902 by itself is _just_ a scsi chip. Any RAID functionality comes either from software drivers or extra hardware[1]. Adaptec has two product lines involving the 7902 chip and RAID. The 'HostRAID' line is just a standard 7902 combined with software RAID drivers for levels 0, 1, and 10, and a BIOS that supports booting off of these levels. The 2200S and 2120S cards are hardware RAID and can do 0, 1, 5, 10, and 50. Scott [1] The marketing literature for the 7902 will say that it contains features that accelerate RAID 1. This still means that it has to have a software driver doing the rest of the work. From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 08:52:33 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CABAA37B401; Wed, 23 Jul 2003 08:52:33 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id B788143FAF; Wed, 23 Jul 2003 08:52:32 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.20) id 19fLuo-00013a-Pc; Wed, 23 Jul 2003 17:52:30 +0200 Date: Wed, 23 Jul 2003 17:52:30 +0200 From: Sheldon Hearn To: Scott Long Message-ID: <20030723155230.GG792@starjuice.net> Mail-Followup-To: Scott Long , freebsd-scsi@freebsd.org References: <20030723084510.GC32528@starjuice.net> <3F1EA458.3020106@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F1EA458.3020106@freebsd.org> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: freebsd-scsi@freebsd.org Subject: Re: Can Adaptec AIC-7902 do RAID-5? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 15:52:34 -0000 On (2003/07/23 09:06), Scott Long wrote: > A 7902 by itself is _just_ a scsi chip. Any RAID functionality comes > either from software drivers or extra hardware[1]. Adaptec has two > product lines involving the 7902 chip and RAID. The 'HostRAID' line > is just a standard 7902 combined with software RAID drivers for levels > 0, 1, and 10, and a BIOS that supports booting off of these levels. > The 2200S and 2120S cards are hardware RAID and can do 0, 1, 5, 10, and > 50. Great Scott! ;-) Thanks, Sheldon. From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 10:35:34 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CD0937B401 for ; Wed, 23 Jul 2003 10:35:34 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 8852E43F85 for ; Wed, 23 Jul 2003 10:35:33 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 39629 invoked by uid 1000); 23 Jul 2003 17:35:34 -0000 Date: Wed, 23 Jul 2003 10:35:34 -0700 (PDT) From: Nate Lawson To: Andrew Heybey In-Reply-To: <85vfttl7r9.fsf@stiegl.mj.niksun.com> Message-ID: <20030723103100.E39567@root.org> References: <200307231125.h6NBPiIS038040@dt.home> <85vfttl7r9.fsf@stiegl.mj.niksun.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: scsi@freebsd.org Subject: Re: probing LUN's X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 17:35:34 -0000 On Wed, 23 Jul 2003, Andrew Heybey wrote: > >>On Wed, 23 Jul 2003 21:25:44 +1000 (EST), Tony Maher said: > tonymaher> Hello, I have been attempting to get a Hitachi SAN > tonymaher> attached to a FreeBSD box via a Qlogic 2300 card. The > tonymaher> card appeared to work ok (as evidenced by verbose boot > tonymaher> messages but no disk(s) was seen. Finally was able to > tonymaher> see disk with a 'camcontrol rescan 1:0:4' > tonymaher> command. Previous 'camcontrol rescan all' and 'camcontrol > tonymaher> rescan 1' failed to see disk. (and obviously not seen at > tonymaher> boot time). > > tonymaher> I did not set the SAN up but from a cursory examination: > tonymaher> The SAN has two controllers and two 'logical' raid 5 > tonymaher> devices. One controller is connected to a Sun box which > tonymaher> sees c1t0d[0-3] and the 4th lun appears to be given over > tonymaher> to the second controller for the FreeBSD box. > > tonymaher> I assume this means that CAM does not probe all LUN's if > tonymaher> no device at LUN 0 or sys/cam/cam_xpt.c has quirk entry > tonymaher> for device that disables LUN probing. There is quirk for > tonymaher> {"HITACHI", "DK31*"} but the SAN reports as Hitachi > tonymaher> DF600F (I think, sorry its at work and I cannot access it > tonymaher> currently) so the second case shouldn't be a problem. > > You need the ispfw driver (either compiled-in or modloaded) to probe > luns beyond LUN 0 for the QLogic FC card. If that is not your > problem, then I do not know... That's true. However, if camcontrol rescan 1:0:4 works for him, then he can try setting CAM_QUIRK_HILUNS for his device to get other luns probed when 0 doesn't respond. -Nate From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 11:02:50 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6851737B401 for ; Wed, 23 Jul 2003 11:02:50 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6164543F3F for ; Wed, 23 Jul 2003 11:02:47 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h6NI2gYU053513; Wed, 23 Jul 2003 12:02:42 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h6NI2fZN053512; Wed, 23 Jul 2003 12:02:41 -0600 (MDT) (envelope-from ken) Date: Wed, 23 Jul 2003 12:02:41 -0600 From: "Kenneth D. Merry" To: Nate Lawson Message-ID: <20030723180241.GA53387@panzer.kdm.org> References: <200307231125.h6NBPiIS038040@dt.home> <85vfttl7r9.fsf@stiegl.mj.niksun.com> <20030723103100.E39567@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723103100.E39567@root.org> User-Agent: Mutt/1.4.1i cc: scsi@freebsd.org Subject: Re: probing LUN's X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 18:02:50 -0000 On Wed, Jul 23, 2003 at 10:35:34 -0700, Nate Lawson wrote: > On Wed, 23 Jul 2003, Andrew Heybey wrote: > > >>On Wed, 23 Jul 2003 21:25:44 +1000 (EST), Tony Maher said: > > tonymaher> Hello, I have been attempting to get a Hitachi SAN > > tonymaher> attached to a FreeBSD box via a Qlogic 2300 card. The > > tonymaher> card appeared to work ok (as evidenced by verbose boot > > tonymaher> messages but no disk(s) was seen. Finally was able to > > tonymaher> see disk with a 'camcontrol rescan 1:0:4' > > tonymaher> command. Previous 'camcontrol rescan all' and 'camcontrol > > tonymaher> rescan 1' failed to see disk. (and obviously not seen at > > tonymaher> boot time). > > > > tonymaher> I did not set the SAN up but from a cursory examination: > > tonymaher> The SAN has two controllers and two 'logical' raid 5 > > tonymaher> devices. One controller is connected to a Sun box which > > tonymaher> sees c1t0d[0-3] and the 4th lun appears to be given over > > tonymaher> to the second controller for the FreeBSD box. > > > > tonymaher> I assume this means that CAM does not probe all LUN's if > > tonymaher> no device at LUN 0 or sys/cam/cam_xpt.c has quirk entry > > tonymaher> for device that disables LUN probing. There is quirk for > > tonymaher> {"HITACHI", "DK31*"} but the SAN reports as Hitachi > > tonymaher> DF600F (I think, sorry its at work and I cannot access it > > tonymaher> currently) so the second case shouldn't be a problem. > > > > You need the ispfw driver (either compiled-in or modloaded) to probe > > luns beyond LUN 0 for the QLogic FC card. If that is not your > > problem, then I do not know... > > That's true. However, if camcontrol rescan 1:0:4 works for him, then he > can try setting CAM_QUIRK_HILUNS for his device to get other luns probed > when 0 doesn't respond. Actually, I don't know that that will cause the device on LUN 4 to show up if LUN 0 isn't probing. According to SAM-3, all SCSI devices must accept LUN 0 as a valid address. Of course if it does respond on LUN 0, but just says that the LUN isn't connected, we may still end up failing to probe additional LUNs.. It has been a while since I looked at the probe code. It's worth a try, though. I'm curious to hear whether that does the trick or not. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 14:00:43 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8974D37B404 for ; Wed, 23 Jul 2003 14:00:43 -0700 (PDT) Received: from c210-49-151-50.thorn1.nsw.optusnet.com.au (c210-49-151-50.thorn1.nsw.optusnet.com.au [210.49.151.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50C0943F93 for ; Wed, 23 Jul 2003 14:00:42 -0700 (PDT) (envelope-from tonymaher@optushome.com.au) Received: from dt.home (localhost [127.0.0.1]) ESMTP id h6NL0ex2099389; Thu, 24 Jul 2003 07:00:40 +1000 (EST) (envelope-from tonym@dt.home) Received: (from tonym@localhost) by dt.home (8.12.9/8.12.9/Submit) id h6NL0YBv099356; Thu, 24 Jul 2003 07:00:35 +1000 (EST) (envelope-from tonym) Date: Thu, 24 Jul 2003 07:00:35 +1000 (EST) From: Tony Maher Message-Id: <200307232100.h6NL0YBv099356@dt.home> To: ath@niksun.com, nate@root.org In-Reply-To: <20030723103100.E39567@root.org> cc: scsi@freebsd.org Subject: Re: probing LUN's X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 21:00:44 -0000 On Thu Jul 24 2003 Nate Lawson wote: > On Wed, 23 Jul 2003, Andrew Heybey wrote: >>>>On Wed, 23 Jul 2003 21:25:44 +1000 (EST), Tony Maher said: >> tonymaher> I assume this means that CAM does not probe all LUN's if >> tonymaher> no device at LUN 0 or sys/cam/cam_xpt.c has quirk entry >> tonymaher> for device that disables LUN probing. There is quirk for >> tonymaher> {"HITACHI", "DK31*"} but the SAN reports as Hitachi >> tonymaher> DF600F (I think, sorry its at work and I cannot access it >> tonymaher> currently) so the second case shouldn't be a problem. >> >> You need the ispfw driver (either compiled-in or modloaded) to probe >> luns beyond LUN 0 for the QLogic FC card. If that is not your >> problem, then I do not know... Whether I use ispfw or the onboard firmware, I still need explicit camcontrol. > That's true. However, if camcontrol rescan 1:0:4 works for him, then he > can try setting CAM_QUIRK_HILUNS for his device to get other luns probed > when 0 doesn't respond. I will checkout this quirk setting. However in private email with Matthew Jacob, he confirms my suscpicions: > If you haven't gotten anything at lun 0, the scan, in the CAM layer in > FreeBSD, won't scan further. See cam_xpt.c around line 5000: > > if ((lun_id != 0) || (device != NULL)) { > if (lun_id < (CAM_SCSI2_MAXLUN-1) || phl) > lun_id++; > } > So, if the probe fails for lun_id == 0, then the scan terminates. thanks for the suggestions. -- tonym From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 23:33:48 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4126F37B401 for ; Wed, 23 Jul 2003 23:33:48 -0700 (PDT) Received: from mail.econolodgetulsa.com (mail.econolodgetulsa.com [198.78.66.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C11F543F3F for ; Wed, 23 Jul 2003 23:33:47 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Received: from mail (user@mail [198.78.66.163])h6O6XnnW011721 for ; Wed, 23 Jul 2003 23:33:49 -0700 (PDT) (envelope-from user@mail.econolodgetulsa.com) Date: Wed, 23 Jul 2003 23:33:49 -0700 (PDT) From: Josh Brooks To: freebsd-scsi@freebsd.org Message-ID: <20030723233123.F10699-100000@mail.econolodgetulsa.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: aaccli: what kind of disk is it ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 06:33:48 -0000 I have studied the help/usage for aaccli for quite a while, and I cannot figure out how to do two things: a) how can I determine the actual, real size of the disk ? For instance, I have some 36gig drives that are 36.8 gigs unformatted size, and some that are 36.4, and so on - if I want to buy a replacement drive to, say, rebuild a mirror, I have to get one that is the same size or larger - so how, in aaccli, can I see the actual unformatted size of that disk ? b) the type of disk it is ... this would be good enough that I wouldn't need (a), since I could just look it up on the `net. Is there a way to see the manufacturer ID string from aaccli - the string that I am shown in the BIOS and when the system boots ? thanks!! From owner-freebsd-scsi@FreeBSD.ORG Wed Jul 23 23:41:05 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38E5637B401 for ; Wed, 23 Jul 2003 23:41:05 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8EAA43F85 for ; Wed, 23 Jul 2003 23:41:03 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 19fY2E-0001O2-00; Wed, 23 Jul 2003 21:48:58 -0700 Date: Wed, 23 Jul 2003 21:48:57 -0700 (PDT) From: Tom Samplonius To: Josh Brooks In-Reply-To: <20030723233123.F10699-100000@mail.econolodgetulsa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: aaccli: what kind of disk is it ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 06:41:05 -0000 On Wed, 23 Jul 2003, Josh Brooks wrote: > I have studied the help/usage for aaccli for quite a while, and I cannot > figure out how to do two things: > > a) how can I determine the actual, real size of the disk ? For instance, > I have some 36gig drives that are 36.8 gigs unformatted size, and some > that are 36.4, and so on - if I want to buy a replacement drive to, say, > rebuild a mirror, I have to get one that is the same size or larger - so > how, in aaccli, can I see the actual unformatted size of that disk ? Most RAID devices do rounding: 4, 9, 18, 36, 72, etc. So if the device is a fraction bigger, it just rounds its capacity down to the standard size. Besides, if you are doing RAID1 or RAID5, the controller can only use as much capacity as the smallest disk in the set. So, if you mirror a 9GB and 18GB, you will only get a 9GB set. > b) the type of disk it is ... this would be good enough that I wouldn't > need (a), since I could just look it up on the `net. Is there a way to > see the manufacturer ID string from aaccli - the string that I am shown in > the BIOS and when the system boots ? > > thanks!! Tom From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 24 04:01:39 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E358637B401 for ; Thu, 24 Jul 2003 04:01:38 -0700 (PDT) Received: from c210-49-151-50.thorn1.nsw.optusnet.com.au (c210-49-151-50.thorn1.nsw.optusnet.com.au [210.49.151.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D07DA43FB1 for ; Thu, 24 Jul 2003 04:01:37 -0700 (PDT) (envelope-from tonymaher@optushome.com.au) Received: from dt.home (localhost [127.0.0.1]) ESMTP id h6OB1ax2023351; Thu, 24 Jul 2003 21:01:36 +1000 (EST) (envelope-from tonym@dt.home) Received: (from tonym@localhost) by dt.home (8.12.9/8.12.9/Submit) id h6OB1RmI023235; Thu, 24 Jul 2003 21:01:27 +1000 (EST) (envelope-from tonym) Date: Thu, 24 Jul 2003 21:01:27 +1000 (EST) From: Tony Maher Message-Id: <200307241101.h6OB1RmI023235@dt.home> To: ken@kdm.org, nate@root.org In-Reply-To: <20030723180241.GA53387@panzer.kdm.org> cc: scsi@freebsd.org Subject: Re: probing LUN's X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 11:01:39 -0000 Hello, > On Thu Jul 24 04:09:59 2003 "Kenneth D. Merry" wrote: > On Wed, Jul 23, 2003 at 10:35:34 -0700, Nate Lawson wrote: >> On Wed, 23 Jul 2003, Andrew Heybey wrote: >>>On Wed, 23 Jul 2003 21:25:44 +1000 (EST), Tony Maher said: >>> tonymaher> I assume this means that CAM does not probe all LUN's if >>> tonymaher> no device at LUN 0 or sys/cam/cam_xpt.c has quirk entry >>> tonymaher> for device that disables LUN probing. There is quirk for >>> tonymaher> {"HITACHI", "DK31*"} but the SAN reports as Hitachi >>> tonymaher> DF600F (I think, sorry its at work and I cannot access it >>> tonymaher> currently) so the second case shouldn't be a problem. >>> >>> You need the ispfw driver (either compiled-in or modloaded) to probe >>> luns beyond LUN 0 for the QLogic FC card. If that is not your >>> problem, then I do not know... >> >> That's true. However, if camcontrol rescan 1:0:4 works for him, then he >> can try setting CAM_QUIRK_HILUNS for his device to get other luns probed >> when 0 doesn't respond. > > Actually, I don't know that that will cause the device on LUN 4 to show up > if LUN 0 isn't probing. According to SAM-3, all SCSI devices must accept > LUN 0 as a valid address. > > Of course if it does respond on LUN 0, but just says that the LUN isn't > connected, we may still end up failing to probe additional LUNs.. It has > been a while since I looked at the probe code. > > It's worth a try, though. I'm curious to hear whether that does the trick > or not. Attempts to use CAM_QUIRK_HILUNS were not successful. Following Matt Jacobs pointer to the code I modified cam_xpt.c *** Warning - cut'n'paste *** --- cam_xpt.c Thu Jul 24 01:58:46 2003 +++ cam_xpt.c.orig Wed Jul 23 23:23:02 2003 @@ -5247,14 +5247,10 @@ device = TAILQ_NEXT(device, links); } splx(s); - if (lun_id < (CAM_SCSI2_MAXLUN-1) || phl) - lun_id++; -/* if ((lun_id != 0) || (device != NULL)) { if (lun_id < (CAM_SCSI2_MAXLUN-1) || phl) lun_id++; } -*/ } else { struct cam_ed *device; And now it finds the HITACHI disk at boot. I am not sure what you mean by "LUN 4 to show up > if LUN 0 isn't probing". There is no device at LUN 0 so the probe will return no device. The existing code gives up further probing at this point (no device at lun 0). This would appear to be a bug. Some background on the SAN setup. There are two controllers, one direct connect to Sun box one direct connect to FreeBSD box There are two 'logical' raid 5 sets, one assigned to each controller. On the Sun it sees LUNS 0-3, and FreeBSD sees LUN 4. It would appear that there is just on physical raid 5 but it is subdivided. I also learnt today from my colleague that you can map LUN 4 to LUN 0 on the second controller (at least to the host freebsd box it will be at LUN 0). However given likelyhood of more SAN devices in future (with 'strange' configurations) it would be nice if FreeBSD probed all LUNs. It isn't a big cost is it? If it is could we have a kernel option CAM_PROBE_ALL_LUNS? thanks for your time -- tonym From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 24 10:00:39 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F87437B401 for ; Thu, 24 Jul 2003 10:00:39 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EB4143FAF for ; Thu, 24 Jul 2003 10:00:38 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h6OH0bo08383; Thu, 24 Jul 2003 10:00:37 -0700 Received: from freebsd.org (hollin.btc.adaptec.com [10.100.253.56]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id KAA02195; Thu, 24 Jul 2003 10:00:37 -0700 (PDT) Message-ID: <3F201027.3080605@freebsd.org> Date: Thu, 24 Jul 2003 10:58:15 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Samplonius References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: Josh Brooks Subject: Re: aaccli: what kind of disk is it ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:00:39 -0000 Tom Samplonius wrote: > On Wed, 23 Jul 2003, Josh Brooks wrote: > > >>I have studied the help/usage for aaccli for quite a while, and I cannot >>figure out how to do two things: >> >>a) how can I determine the actual, real size of the disk ? For instance, >>I have some 36gig drives that are 36.8 gigs unformatted size, and some >>that are 36.4, and so on - if I want to buy a replacement drive to, say, >>rebuild a mirror, I have to get one that is the same size or larger - so >>how, in aaccli, can I see the actual unformatted size of that disk ? > > > Most RAID devices do rounding: 4, 9, 18, 36, 72, etc. So if the device > is a fraction bigger, it just rounds its capacity down to the standard > size. Not true. > Besides, if you are doing RAID1 or RAID5, the controller can only > use as much capacity as the smallest disk in the set. So, if you mirror > a 9GB and 18GB, you will only get a 9GB set. > The point of the question was that if a failed disk is replaced with one that is fractionally smaller, it won't work. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 24 10:05:34 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DC8837B401 for ; Thu, 24 Jul 2003 10:05:34 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2141E43F75 for ; Thu, 24 Jul 2003 10:05:34 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h6OH5Yo11692; Thu, 24 Jul 2003 10:05:34 -0700 Received: from freebsd.org (hollin.btc.adaptec.com [10.100.253.56]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id KAA04421; Thu, 24 Jul 2003 10:05:33 -0700 (PDT) Message-ID: <3F201153.1050601@freebsd.org> Date: Thu, 24 Jul 2003 11:03:15 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Brooks References: <20030723233123.F10699-100000@mail.econolodgetulsa.com> In-Reply-To: <20030723233123.F10699-100000@mail.econolodgetulsa.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: aaccli: what kind of disk is it ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:05:34 -0000 Josh Brooks wrote: > I have studied the help/usage for aaccli for quite a while, and I cannot > figure out how to do two things: > > > a) how can I determine the actual, real size of the disk ? For instance, > I have some 36gig drives that are 36.8 gigs unformatted size, and some > that are 36.4, and so on - if I want to buy a replacement drive to, say, > rebuild a mirror, I have to get one that is the same size or larger - so > how, in aaccli, can I see the actual unformatted size of that disk ? > > b) the type of disk it is ... this would be good enough that I wouldn't > need (a), since I could just look it up on the `net. Is there a way to > see the manufacturer ID string from aaccli - the string that I am shown in > the BIOS and when the system boots ? > > thanks!! > Try using the aaccli command 'disk list /full'. That will give you the vendor, model, and revision numbers from the standard inquiry information. It will also tell you how many sectors (blocks) the disk has. However, I'm not 100% sure if this number is completely accurate; drives that have been initialized by the adapter have their first 128 sectors reserved. Another path for determining this information would be to enable the 'aacp' device. This will present all of the physical disks behind the card as SCSI 'passthrough' devices. You can then use camcontrol(8) to send standard SCSI command like INQUIRY to the disks and verify their response. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 24 10:38:22 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21A6B37B401; Thu, 24 Jul 2003 10:38:22 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A0B43FA3; Thu, 24 Jul 2003 10:38:18 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 19fiII-0001q9-00; Thu, 24 Jul 2003 08:46:14 -0700 Date: Thu, 24 Jul 2003 08:46:13 -0700 (PDT) From: Tom Samplonius To: Scott Long In-Reply-To: <3F201027.3080605@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: Josh Brooks Subject: Re: aaccli: what kind of disk is it ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 17:38:22 -0000 On Thu, 24 Jul 2003, Scott Long wrote: > Tom Samplonius wrote: > > On Wed, 23 Jul 2003, Josh Brooks wrote: > > > >>I have studied the help/usage for aaccli for quite a while, and I cannot > >>figure out how to do two things: > >> > >>a) how can I determine the actual, real size of the disk ? For instance, > >>I have some 36gig drives that are 36.8 gigs unformatted size, and some > >>that are 36.4, and so on - if I want to buy a replacement drive to, say, > >>rebuild a mirror, I have to get one that is the same size or larger - so > >>how, in aaccli, can I see the actual unformatted size of that disk ? > > > > > > Most RAID devices do rounding: 4, 9, 18, 36, 72, etc. So if the device > > is a fraction bigger, it just rounds its capacity down to the standard > > size. > > Not true. Really? I've never seen one that didn't. Replacing disks is a basic requirement of RAID, so it seems odd that anyone would want to make it hard to do. Do you know the which devices don't do this? > > Besides, if you are doing RAID1 or RAID5, the controller can only > > use as much capacity as the smallest disk in the set. So, if you mirror > > a 9GB and 18GB, you will only get a 9GB set. > > > > The point of the question was that if a failed disk is replaced with one > that is fractionally smaller, it won't work. > > Scott Tom From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 24 12:14:43 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7B7837B404 for ; Thu, 24 Jul 2003 12:14:43 -0700 (PDT) Received: from maine.60north.net (maine.60north.net [198.143.201.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F7B843FAF for ; Thu, 24 Jul 2003 12:14:41 -0700 (PDT) (envelope-from jackp@flag.60north.net) Received: from wms1.60north.net (mws1.60north.net [198.143.201.200]) by maine.60north.net (8.11.3/8.11.3) with SMTP id h6OJEde62353 for ; Thu, 24 Jul 2003 15:14:39 -0400 (EDT) Received: FROM flag.60north.net BY wms1.60north.net ; Thu Jul 24 15:05:44 2003 -0700 Received: from admin.60north.net by flag.60north.net id aa15677; 24 Jul 2003 15:11 EDT Date: Thu, 24 Jul 2003 19:11:11 -0000 To: , , , From: Jack Patton X-Mailer: TWIG 2.7.6 Message-ID: <200307241511.aa15677@flag.60north.net> Subject: Re: kern/53566: IBM Eserver (245 || 345) + ServeRaid 5i ips driver panic X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jackp@flag.60north.net List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 19:14:44 -0000 No good with the 0708 snap. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT-20030708-JPSNAP #0: Tue Jul 8 00:26:27 GMT 2003 root@ushi.jp.freebsd.org:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0b65000. Preloaded mfs_root "/boot/mfsroot" at 0xc0b65278. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0b652bc. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2793894552 Hz CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.89-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 526385152 (502 MB) avail memory = 499220480 (476 MB) Pentium Pro MTRR support enabled md0: Preloaded image 4423680 bytes at 0xc06e1068 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib0: slot 9 INTA is routed to irq 10 pcib0: slot 15 INTA is routed to irq 11 pci0: at device 9.0 (no driver attached) atapci0: port 0x700-0x70f,0x374- 0x377,0x17 0-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: simplex device, DMA on primary only ata1: at 0x170 irq 15 on atapci0 ohci0: mem 0xfebfe000-0xfebfefff irq 11 at devic e 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: on acpi0 pci2: on pcib1 pcib1: slot 8 INTA is routed to irq 3 bge0: mem 0xfbff0000- 0xfb ffffff irq 3 at device 8.0 on pci2 bge0: Ethernet address: 00:09:6b:a5:18:05 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX -FDX, auto pcib2: on acpi0 pci5: on pcib2 pcib2: slot 3 INTA is routed to irq 9 ips0: mem 0xf4000000-0xf7ffffff irq 9 at device 3.0 on p ci5 ips0: logical drives: 222 ipsd0: on ips0 ipsd0: Logical Drive (1824184MB) ipsd1: on ips0 ipsd1: Logical Drive (1824184MB) ipsd2: on ips0 ipsd2: Logical Drive (1824184MB) ipsd3: on ips0 ipsd3: Logical Drive (1824184MB) ipsd4: on ips0 ipsd4: Logical Drive (1824184MB) ipsd5: on ips0 ipsd5: Logical Drive (1824184MB) ipsd6: on ips0 ipsd6: Logical Drive (1824184MB) ipsd7: on ips0 ipsd7: Logical Drive (1824184MB) pcib3: on acpi0 pci7: on pcib3 pcib4: on acpi0 pci9: on pcib4 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: unable to set the command byte. device_probe_and_attach: atkbd0 attach returned 6 psm: failed to restore the keyboard controller command byte. psm0: unable to set the command byte. fdc0: port 0x3f7,0x3f0-0 x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console orm0: