From owner-freebsd-scsi Sun Mar 3 6:45:42 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 8CDC837B400; Sun, 3 Mar 2002 06:45:36 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA16023; Sun, 3 Mar 2002 09:45:27 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id JAA11383; Sun, 3 Mar 2002 09:45:25 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA11379; Sun, 3 Mar 2002 09:45:25 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sun, 3 Mar 2002 09:45:25 -0500 (EST) From: Kenneth Wayne Culver To: "Kenneth D. Merry" Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: scsi problems In-Reply-To: <20020302222346.A99780@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Well, I tried that, but I ended up needing another jumper to terminate the last drive. Also, for some reason, now that I have it working; I set one drive to ID 0 and one to ID 1, but for some reason the SCSI chip finds these as ID 1 and ID 2... which I find a bit odd. Ken On Sat, 2 Mar 2002, Kenneth D. Merry wrote: > On Sat, Mar 02, 2002 at 23:48:58 -0500, Kenneth Wayne Culver wrote: > > > Ding ding ding ding! > > > > > > I think we have a winner. > > > > > > Find some more jumpers, and make sure you've got a unique ID. > > > > > > I doubt SCAM is supported by the ahc driver (or many, if any of the other > > > SCSI drivers). > > > > > Ohhhh mann.... I thought that this was a hardware feature, I didn't > > realize that it was driver dependent... Do you know if it'll ever be > > supported? I have no idea where to find jumpers for these drives... I > > kinda got the second-hand... > > I don't know, ask Justin Gibbs . > > As for the jumpers, there are generally two sizes of jumpers on most > drives, and you can usually find some that fit well enough on some piece of > hardware or other. > > All you probably need is one jumper for the ID, though. (None for one > drive, and 1 to make the other one ID 1, 2, 4 or 8.) > > 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 Sun Mar 3 6:46:51 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id BDB5F37B400; Sun, 3 Mar 2002 06:46:46 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA16372; Sun, 3 Mar 2002 09:46:45 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id JAA11532; Sun, 3 Mar 2002 09:46:44 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA11528; Sun, 3 Mar 2002 09:46:44 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sun, 3 Mar 2002 09:46:44 -0500 (EST) From: Kenneth Wayne Culver To: Michael Smith Cc: "Kenneth D. Merry" , freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: scsi problems In-Reply-To: <200203030554.g235sHx04073@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > It's not, really. Drives set up using SCAM should be configured by your > BIOS, unless there's some reason that you've completely disabled the BIOS > on this controller. > Well, the BIOS found them fine, and even assigned SCSI ID's to them... but FreeBSD would only see the one at ID 0... But I have it working with jumpers now, so it doesn't matter... Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 9: 5:46 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id D74CC37B405; Sun, 3 Mar 2002 09:05:41 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g23H6uI00782; Sun, 3 Mar 2002 10:06:57 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200203031706.g23H6uI00782@aslan.scsiguy.com> To: Michael Smith Cc: Kenneth Wayne Culver , "Kenneth D. Merry" , freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: scsi problems In-Reply-To: Your message of "Sat, 02 Mar 2002 21:54:17 PST." <200203030554.g235sHx04073@mass.dis.org> Date: Sun, 03 Mar 2002 10:06:56 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >It's not, really. Drives set up using SCAM should be configured by your >BIOS, unless there's some reason that you've completely disabled the BIOS >on this controller. I've never taken the time to read the SCAM spec as it is deprecated in SPI3 and above, but you may have to reSCAM after every bus reset in order to keep the IDs. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 13: 6:46 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id A4CF137B405 for ; Sun, 3 Mar 2002 13:06:43 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.11.6/8.11.6) with ESMTP id g23L6eM42491; Sun, 3 Mar 2002 16:06:40 -0500 (EST) (envelope-from winter@jurai.net) Date: Sun, 3 Mar 2002 16:06:40 -0500 (EST) From: "Matthew N. Dodd" To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: <20020303144103.T1640-100000@gerard> Message-ID: <20020303160107.S95839-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 3 Mar 2002, [ISO-8859-1] Gérard Roudier wrote: > I read that you have been suggested to update the drive firmware. It is > indeed the best thing to do. I'd love to have that option but tracking down SEAGATE firmware updates is next to impossible. > You could also hack the driver source for it to accept the condition, > but I would not be happy to help you for that given that the firmware > bug you have been told about is likely the cause. Gee, thats helpful. I could also switch to hardware whose driver correctly interoperates with my hardware. It would be wonderful if we lived in a perfect world and nobody wrote non-conforming firmware, but that just isn't the case and pretending it is seems foolish. If I do manage to come up with a patch that "fixes" this problem I'll be sure to run it by you but I will commit it. More likely is that I'll just yank the card and not waste any more time. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 13:14:42 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 91C3F37B402 for ; Sun, 3 Mar 2002 13:14:37 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g23LFnI02625; Sun, 3 Mar 2002 14:15:49 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200203032115.g23LFnI02625@aslan.scsiguy.com> To: "Matthew N. Dodd" Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: Your message of "Sun, 03 Mar 2002 16:06:40 EST." <20020303160107.S95839-100000@sasami.jurai.net> Date: Sun, 03 Mar 2002 14:15:49 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> You could also hack the driver source for it to accept the condition, >> but I would not be happy to help you for that given that the firmware >> bug you have been told about is likely the cause. > >Gee, thats helpful. > >I could also switch to hardware whose driver correctly interoperates with >my hardware. Its not really clear to me why one driver works and the other does not. Both should be flagging the overrun as an error. Perhaps in 3.4, the ahc driver was broken in this regard? Does a more recent ahc driver still work? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 13:19: 1 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 1508F37B405 for ; Sun, 3 Mar 2002 13:18:58 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.11.6/8.11.6) with ESMTP id g23LIsM43397; Sun, 3 Mar 2002 16:18:54 -0500 (EST) (envelope-from winter@jurai.net) Date: Sun, 3 Mar 2002 16:18:54 -0500 (EST) From: "Matthew N. Dodd" To: "Justin T. Gibbs" Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: <200203032115.g23LFnI02625@aslan.scsiguy.com> Message-ID: <20020303161602.I95839-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 3 Mar 2002, Justin T. Gibbs wrote: > Its not really clear to me why one driver works and the other does not. > Both should be flagging the overrun as an error. Perhaps in 3.4, the > ahc driver was broken in this regard? Does a more recent ahc driver > still work? I've not yet tried the drives with a recent version of 'ahc'. The hardware is kinda buried in a rack right now. If I had to guess at the difference I'd say that this bit of code from sym_hipd.c is the reason for the difference: static void sym_sir_bad_scsi_status(hcb_p np, int num, ccb_p cp) { ... /* * Now deal with the SCSI status. */ switch(s_status) { ... case S_TERMINATED: case S_CHECK_COND: /* * If we get an SCSI error when requesting sense, give up. */ if (h_flags & HF_SENSE) { sym_complete_error (np, cp); break; } ... I'm mostly guessing at this point though. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 13:26:22 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 5C97B37B400 for ; Sun, 3 Mar 2002 13:26:20 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g23LRXI03420; Sun, 3 Mar 2002 14:27:33 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200203032127.g23LRXI03420@aslan.scsiguy.com> To: "Matthew N. Dodd" Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: Your message of "Sun, 03 Mar 2002 16:18:54 EST." <20020303161602.I95839-100000@sasami.jurai.net> Date: Sun, 03 Mar 2002 14:27:33 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >I've not yet tried the drives with a recent version of 'ahc'. The >hardware is kinda buried in a rack right now. > >If I had to guess at the difference I'd say that this bit of code from >sym_hipd.c is the reason for the difference: > >static void sym_sir_bad_scsi_status(hcb_p np, int num, ccb_p cp) >{ >... > /* > * Now deal with the SCSI status. > */ > switch(s_status) { >... > case S_TERMINATED: > case S_CHECK_COND: > /* > * If we get an SCSI error when requesting sense, give up. > */ > if (h_flags & HF_SENSE) { > sym_complete_error (np, cp); > break; > } > ... Other than needing to complete the transaction with CAM_AUTOSENSE_FAIL, the ahc driver does something very similar. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 14: 0:38 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id BFF7237B405 for ; Sun, 3 Mar 2002 14:00:36 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.11.6/8.11.6) with ESMTP id g23M0XM45118; Sun, 3 Mar 2002 17:00:33 -0500 (EST) (envelope-from winter@jurai.net) Date: Sun, 3 Mar 2002 17:00:33 -0500 (EST) From: "Matthew N. Dodd" To: "Justin T. Gibbs" Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: <200203032127.g23LRXI03420@aslan.scsiguy.com> Message-ID: <20020303165947.G95839-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 3 Mar 2002, Justin T. Gibbs wrote: > Other than needing to complete the transaction with CAM_AUTOSENSE_FAIL, > the ahc driver does something very similar. The 'ahc' driver detects these drives under -CURRENT without any sort of error at all. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 14: 6:58 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 02F9637B400 for ; Sun, 3 Mar 2002 14:06:54 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g23M86I05088; Sun, 3 Mar 2002 15:08:06 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200203032208.g23M86I05088@aslan.scsiguy.com> To: "Matthew N. Dodd" Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: Your message of "Sun, 03 Mar 2002 17:00:33 EST." <20020303165947.G95839-100000@sasami.jurai.net> Date: Sun, 03 Mar 2002 15:08:06 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >On Sun, 3 Mar 2002, Justin T. Gibbs wrote: >> Other than needing to complete the transaction with CAM_AUTOSENSE_FAIL, >> the ahc driver does something very similar. > >The 'ahc' driver detects these drives under -CURRENT without any sort of >error at all. The overrun messages are gone? Weird. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 15: 3:53 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 0976037B405 for ; Sun, 3 Mar 2002 15:03:50 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.11.6/8.11.6) with ESMTP id g23N3lM48661; Sun, 3 Mar 2002 18:03:47 -0500 (EST) (envelope-from winter@jurai.net) Date: Sun, 3 Mar 2002 18:03:47 -0500 (EST) From: "Matthew N. Dodd" To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG, Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: <20020303234023.F2892-100000@gerard> Message-ID: <20020303180031.T95839-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 3 Mar 2002, [ISO-8859-1] Gérard Roudier wrote: > I will look more into this problem to-morrow evening. You may let me > know any additionnal information that seems useful to you. Thanks. I've got no information other than what I posted. I've replaced the 'sym' board with a 'ahc' board as this system needs to be operational ASAP. Thankfully this problem should be easy to reproduce as "SEAGATE ST410800WSUN9.0G 0407" drives are cheap and I assume there is nothing special about my SYM22802 board. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 15: 5: 9 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 68FC037B402 for ; Sun, 3 Mar 2002 15:05:07 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.11.6/8.11.6) with ESMTP id g23N54M48930; Sun, 3 Mar 2002 18:05:04 -0500 (EST) (envelope-from winter@jurai.net) Date: Sun, 3 Mar 2002 18:05:04 -0500 (EST) From: "Matthew N. Dodd" To: "Justin T. Gibbs" Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: <200203032208.g23M86I05088@aslan.scsiguy.com> Message-ID: <20020303180355.P95839-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 3 Mar 2002, Justin T. Gibbs wrote: > The overrun messages are gone? Weird. Indeed. Nothing other than the SCSI card was changed. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 3 15:16:27 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 153B437B402 for ; Sun, 3 Mar 2002 15:16:24 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g23NGJc99353; Mon, 4 Mar 2002 00:16:19 +0100 (CET) (envelope-from wkb) Date: Mon, 4 Mar 2002 00:16:19 +0100 From: Wilko Bulte To: "Matthew N. Dodd" Cc: =?iso-8859-15?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG, gibbs@scsiguy.com Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. Message-ID: <20020304001619.A99336@freebie.xs4all.nl> References: <20020303234023.F2892-100000@gerard> <20020303180031.T95839-100000@sasami.jurai.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20020303180031.T95839-100000@sasami.jurai.net>; from winter@jurai.net on Sun, Mar 03, 2002 at 06:03:47PM -0500 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Mar 03, 2002 at 06:03:47PM -0500, Matthew N. Dodd wrote: > On Sun, 3 Mar 2002, [ISO-8859-1] Gérard Roudier wrote: > > I will look more into this problem to-morrow evening. You may let me > > know any additionnal information that seems useful to you. Thanks. > > I've got no information other than what I posted. > > I've replaced the 'sym' board with a 'ahc' board as this system needs to > be operational ASAP. > > Thankfully this problem should be easy to reproduce as > "SEAGATE ST410800WSUN9.0G 0407" drives are cheap and I assume there is ^--- Sun specific firmware. I've heared mixed stories about what Sun wanted their disk suppliers to put in the drives firmware wise. I cannot speak from my own experience though. Wilko -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 11:20:23 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 4ACF837B41B for ; Mon, 4 Mar 2002 11:20:06 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA19032 for freebsd-scsi@freebsd.org; Mon, 4 Mar 2002 20:20:04 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g24JIPk51918; Mon, 4 Mar 2002 20:18:25 +0100 (MET) (envelope-from j) Date: Mon, 4 Mar 2002 20:18:25 +0100 (MET) Message-Id: <200203041918.g24JIPk51918@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20020303234023.F2892-100000@gerard> <20020303180031.T95839-100000@sasami.jurai.net> <20020304001619.A99336@freebie.xs4all.nl> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wilko Bulte wrote: >> Thankfully this problem should be easy to reproduce as >> "SEAGATE ST410800WSUN9.0G 0407" drives are cheap and I assume there is > > ^--- Sun specific firmware. > > I've heared mixed stories about what Sun wanted their disk suppliers > to put in the drives firmware wise. According to my own experience, they work fine in a PC-ish environment as well, no problems. Disclaimer: i haven't ever tried a HVD drive in a PC-like environment, but i wouldn't assume that to make a difference regarding firware versions. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 11:41:36 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 1095937B402 for ; Mon, 4 Mar 2002 11:41:33 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g24JfTF03020; Mon, 4 Mar 2002 20:41:29 +0100 (CET) (envelope-from wkb) Date: Mon, 4 Mar 2002 20:41:29 +0100 From: Wilko Bulte To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. Message-ID: <20020304204128.A3003@freebie.xs4all.nl> References: <20020303234023.F2892-100000@gerard> <20020303180031.T95839-100000@sasami.jurai.net> <20020304001619.A99336@freebie.xs4all.nl> <200203041918.g24JIPk51918@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200203041918.g24JIPk51918@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Mon, Mar 04, 2002 at 08:18:25PM +0100 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Mar 04, 2002 at 08:18:25PM +0100, Joerg Wunsch wrote: > Wilko Bulte wrote: > > >> Thankfully this problem should be easy to reproduce as > >> "SEAGATE ST410800WSUN9.0G 0407" drives are cheap and I assume there is > > > > ^--- Sun specific firmware. > > > > I've heared mixed stories about what Sun wanted their disk suppliers > > to put in the drives firmware wise. > > According to my own experience, they work fine in a PC-ish environment > as well, no problems. Disclaimer: i haven't ever tried a HVD drive in > a PC-like environment, but i wouldn't assume that to make a difference > regarding firware versions. The electrical interface should be irrelevant, I agree. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 12:20:28 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 8847337B402; Mon, 4 Mar 2002 12:20:09 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id VAA19773; Mon, 4 Mar 2002 21:20:04 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g24KGb553037; Mon, 4 Mar 2002 21:16:37 +0100 (MET) (envelope-from j) Date: Mon, 4 Mar 2002 21:16:37 +0100 (MET) Message-Id: <200203042016.g24KGb553037@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: questions@freebsd.org Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20020302192603.R80295-100000@earl-grey.cloud9.net> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: scsi problems [device x?] X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org, questions@freebsd.org Cc: Peter Leftwich Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [This really belongs to freebsd-questions instead. Please honor the reply-to accordingly.] Peter Leftwich wrote: > SCSI(4) FreeBSD Kernel Interfaces Manual > NAME > SCSI, CAM - CAM SCSI subsystem > SYNOPSIS > device scbus > device scbus1 at ahc0 [snip] > device da > > [1] When manpages refer to a line of text saying "device pcm0" or > whatever, where do they intend for you to enter that text, i.e. in which > file? Please read intro(4). There it's explained that they belong to the kernel config file. > [2] I feel I am using a generic "PnP" kernel, and would like info on > how to recompile (rebuild?) the kernel to only load what is > pertinent to my system, help? Is this difficult, and does it > involve cc/gcc/build? :( Please read the appropriate section of the handbook, it explains it in good detail. You might have installed it locally, somewhere under /usr/share/doc, or just read it at http://www.freebsd.org/handbook/, or one of the mirrors. > On Sat, 2 Mar 2002, Kenneth Wayne Culver wrote: >> Return-Path: >> Received: from mail1.registeredsite.com (mail1.registeredsite.com Oh, please no full quotes, in particular not in such a fairly unrelated case. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 18: 2:56 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.mirapoint.com (mail.mirapoint.com [63.107.133.18]) by hub.freebsd.org (Postfix) with ESMTP id 859E837B400 for ; Mon, 4 Mar 2002 18:02:53 -0800 (PST) Received: from mail.mirapoint.com (localhost.mirapoint.com [127.0.0.1]) by mail.mirapoint.com (Mirapoint Messaging Server MOS 3.1.0.43) with SMTP id AOD05455 (AUTH cer); Mon, 4 Mar 2002 18:02:46 -0800 (PST) Message-Id: <200203050202.AOD05455@mail.mirapoint.com> Received: from 192.168.1.94 by mail.mirapoint.com (Mirapoint Messaging Server MOS 3.1.0.43) with HTTPS/1.1; Mon, 4 Mar 2002 18:03:22 -0800 Date: Mon, 4 Mar 2002 18:03:22 -0800 From: Carl Reisinger Subject: Writing > 64KB records to SCSI Tape, FreeBSD 4.1 (?) To: freebsd-scsi@FreeBSD.org Reply-To: cer@mirapoint.com X-Mailer: Mirapoint Webmail Direct 3.1.0.43 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I would like to write records of 128KB to a SCSI tape device (DLT 7 or 8000, LTO). While MAXPHYS is 128KB, the code in kern_physio:physio will adjust the max size based on the value of dev->si_iosize_max. It my case it appears that this value is 0 (or < PAGE_SIZE), so physio will set si_iosize_max to DFLTPHYS which is defined to be 64KB. In any case DFLTPHYS is the limit I am hitting. This in turn will cause the 128KB write to be broken into two 64KB writes, which just doesn't work for me. The best solution, for me, would be a change to scsi_sa.c that will set si_iosize_max for the device. Can anyone help? NOTE: While most of the kernel is based on 4.1-STABLE, I believe the CAM subsystem and scsi_sa has been lifted from 4.3. (The behaviour is the same under 4.5) Thanks, Carl Reisinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 19:53: 6 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id A6A4E37B41C for ; Mon, 4 Mar 2002 19:53:03 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g253qwM13452; Mon, 4 Mar 2002 20:52:58 -0700 (MST) (envelope-from ken) Date: Mon, 4 Mar 2002 20:52:58 -0700 From: "Kenneth D. Merry" To: Carl Reisinger Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Writing > 64KB records to SCSI Tape, FreeBSD 4.1 (?) Message-ID: <20020304205257.A13402@panzer.kdm.org> References: <200203050202.AOD05455@mail.mirapoint.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200203050202.AOD05455@mail.mirapoint.com>; from cer@mirapoint.com on Mon, Mar 04, 2002 at 06:03:22PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Mar 04, 2002 at 18:03:22 -0800, Carl Reisinger wrote: > I would like to write records of 128KB to a SCSI tape device > (DLT 7 or 8000, LTO). > > While MAXPHYS is 128KB, the code in kern_physio:physio will > adjust the max size based on the value of dev->si_iosize_max. > > It my case it appears that this value is 0 (or < PAGE_SIZE), > so physio will set si_iosize_max to DFLTPHYS which is > defined to be 64KB. In any case DFLTPHYS is the limit I am > hitting. > > This in turn will cause the 128KB write to be broken into > two 64KB writes, which just doesn't work for me. > > The best solution, for me, would be a change to scsi_sa.c > that will set si_iosize_max for the device. > > Can anyone help? 64K is pretty much the lowest common denominator as far as transfer size goes. I believe that's pretty close to what an Adaptec 1542 can handle, so that's why we've left it at that size. (From a CAM standpoint that is.) I would suggest just bumping si_iosize_max up to 128K in your copy of the sa(4) driver and see if that does the trick. > NOTE: While most of the kernel is based on 4.1-STABLE, I > believe the CAM subsystem and scsi_sa has been lifted from > 4.3. (The behaviour is the same under 4.5) Sounds "interesting". :) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 22:10: 3 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 71DD437B416 for ; Mon, 4 Mar 2002 22:09:58 -0800 (PST) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g2566Hr84329 for ; Mon, 4 Mar 2002 22:06:17 -0800 (PST) (envelope-from root@utility.clubscholarship.com) Date: Mon, 4 Mar 2002 22:06:17 -0800 (PST) From: Patrick Thomas To: Subject: Dell PERC scrub / scrubbing question Message-ID: <20020304220244.T84242-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org When I created my mirrors originally with my Dell PERC 2 controller, they immediately started scrubbing. The BIOS told me not to use them until they were done scrubbing. Fair enough. I am now using the system regularly, and it _seems_ that every time I reboot the computer the scrubbing starts over again. Three questions: 1. Am I correct in this assumption ? I know they are scrubbing, because they say they are, but perhaps they are scrubbing for some other reason and I just *think* it is because I rebooted ? 2. Is it dangerous to use the disks while they are scrubbing due to a reboot, just like it was dangerous to use them while they were doing the original scrub ? 3. It seems like performance is way down while they are scrubbing. Am I correct that it is, or am I just making that up ? thanks, PT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 22:42: 2 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.mirapoint.com (mail.mirapoint.com [63.107.133.18]) by hub.freebsd.org (Postfix) with ESMTP id A21D737B400 for ; Mon, 4 Mar 2002 22:41:59 -0800 (PST) Received: from mail.mirapoint.com (localhost.mirapoint.com [127.0.0.1]) by mail.mirapoint.com (Mirapoint Messaging Server MOS 3.1.0.43) with SMTP id AOD06786 (AUTH cer); Mon, 4 Mar 2002 22:41:55 -0800 (PST) Message-Id: <200203050641.AOD06786@mail.mirapoint.com> Received: from 207.135.76.118 by mail.mirapoint.com (Mirapoint Messaging Server MOS 3.1.0.43) with HTTPS/1.1; Mon, 4 Mar 2002 22:42:34 -0800 Date: Mon, 4 Mar 2002 22:42:34 -0800 From: Carl Reisinger Subject: Re: Writing > 64KB records to SCSI Tape, FreeBSD 4.1 (?) To: "Kenneth D. Merry" Cc: Carl Reisinger , freebsd-scsi@FreeBSD.ORG Reply-To: cer@mirapoint.com X-Mailer: Mirapoint Webmail Direct 3.1.0.43 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >I believe that's pretty close to what an Adaptec 1542 can handle, so that's >why we've left it at that size. (From a CAM standpoint that is.) I haven't laid hands or eyes on a 1542 in nearly 8 years. But from watching this list it seems a fair number of people have cards that I haven't seen in years. > >I would suggest just bumping si_iosize_max up to 128K in your copy of the >sa(4) driver and see if that does the trick. > That's what I would like to do, but my knowledge of the sa driver, and FreeBSD drivers in general, is slim. Since sending my original message I have spent more time looking over the code. If I understand things correctly the dev parameter to saopen is actually a pointer to a specinfo structure and I can just change the value of si_iosize_max in saopen. True? If I want to get real fancy I can set si_iosize_max in samount after the max record size supported by the drive is found. (use the min of MAXPHYS and the drive max) (Now if there was a way to query the HBA for its max transfer size). The good news, for me, is that the controllers I need to support is very limited. aic7899 and a few Symbios controllers. The aic7899 seems to handle 16MB transfers. Don't know about the Symbios chips. >> NOTE: While most of the kernel is based on 4.1-STABLE, I >> believe the CAM subsystem and scsi_sa has been lifted from >> 4.3. (The behaviour is the same under 4.5) > >Sounds "interesting". :) > We try to limit "changes", but every so often we need a fix from a later release. And sometimes that involves back porting a fair amount of code. I forget what the 4.1 CAM problem was that caused us to pull in the 4.3 code. Carl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 4 23: 9: 8 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by hub.freebsd.org (Postfix) with ESMTP id 2CC9437B43A for ; Mon, 4 Mar 2002 23:09:00 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 16i8QX-0001qw-00; Mon, 4 Mar 2002 22:27:57 -0800 Date: Mon, 4 Mar 2002 22:27:55 -0800 (PST) From: Tom Samplonius To: Patrick Thomas Cc: freebsd-scsi@freebsd.org Subject: Re: Dell PERC scrub / scrubbing question In-Reply-To: <20020304220244.T84242-100000@utility.clubscholarship.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 4 Mar 2002, Patrick Thomas wrote: > When I created my mirrors originally with my Dell PERC 2 controller, they > immediately started scrubbing. The BIOS told me not to use them until > they were done scrubbing. Fair enough. Depends on what they mean by scrubbing. It usually takes a long time to initialize a RAID5 volume, because the parity is created for the first time. Scrubbing usually refers to reading all blocks, and verifying that the parity matches. This is used to detect bad blocks on a disk. Not all RAID controllers even do this. Scrubbing is important for RAID5, because if a disk develops a bad area where some infrequently accessed files are stored, you might be in for an unpleasent surprise if you try to read them when the array is running degraded. On systems that I've seen that do scrubbing, they always implement it as a low-priority background task as to not to impair normal volume activity. It might be possible to configure the scrubbing priority, as well as the scrubbing schedule. 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 4 23:16:58 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id E4D7937B400 for ; Mon, 4 Mar 2002 23:16:55 -0800 (PST) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g257D9285658; Mon, 4 Mar 2002 23:13:09 -0800 (PST) (envelope-from root@utility.clubscholarship.com) Date: Mon, 4 Mar 2002 23:13:09 -0800 (PST) From: Patrick Thomas To: Tom Samplonius Cc: Subject: Re: Dell PERC scrub / scrubbing question In-Reply-To: Message-ID: <20020304231233.V85161-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org These are mirrors I have created, though...RAID 1. Comments ? (please :) --PT > > When I created my mirrors originally with my Dell PERC 2 controller, they > > immediately started scrubbing. The BIOS told me not to use them until > > they were done scrubbing. Fair enough. > > Depends on what they mean by scrubbing. It usually takes a long time to > initialize a RAID5 volume, because the parity is created for the first > time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 5 9:31:23 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 942EB37B416 for ; Tue, 5 Mar 2002 09:31:06 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g25HV3h17997; Tue, 5 Mar 2002 10:31:03 -0700 (MST) (envelope-from ken) Date: Tue, 5 Mar 2002 10:31:03 -0700 From: "Kenneth D. Merry" To: Carl Reisinger Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Writing > 64KB records to SCSI Tape, FreeBSD 4.1 (?) Message-ID: <20020305103103.A17761@panzer.kdm.org> References: <200203050641.AOD06786@mail.mirapoint.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200203050641.AOD06786@mail.mirapoint.com>; from cer@mirapoint.com on Mon, Mar 04, 2002 at 10:42:34PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Mar 04, 2002 at 22:42:34 -0800, Carl Reisinger wrote: > >I believe that's pretty close to what an Adaptec 1542 can > handle, so that's > >why we've left it at that size. (From a CAM standpoint > that is.) > > I haven't laid hands or eyes on a 1542 in nearly 8 years. > But from watching this list it seems a fair number of people > have cards that I haven't seen in years. Yes, I think Matthew Dodd's Adaptec 4944 may be one of the rarest pieces of hardware I've heard about in a while. IIRC, *very* few of them were made. > > > >I would suggest just bumping si_iosize_max up to 128K in > your copy of the > >sa(4) driver and see if that does the trick. > > > > That's what I would like to do, but my knowledge of the sa > driver, and FreeBSD drivers in general, is slim. > > Since sending my original message I have spent more time > looking over the code. If I understand things correctly the > dev parameter to saopen is actually a pointer to a specinfo > structure and I can just change the value of si_iosize_max > in saopen. True? > > If I want to get real fancy I can set si_iosize_max in > samount after the max record size supported by the drive is > found. (use the min of MAXPHYS and the drive max) I would suggest changing si_iosize_max in saregister() after the various make_dev(). Make sure you change it for each dev_t created. That way, you only end up changing the size once for each device, instead of every time you open/close. > (Now if there was a way to query the HBA for its max > transfer size). We've been planning on doing that, although it may end up being a little more complicated than just asking for a max transfer size. You may have a maximum size, a maximum recommended size, a maximum number of S/G elements, and so forth. Basically the idea would to to figure out what the size restrictions along the I/O path are. > The good news, for me, is that the controllers I need to > support is very limited. aic7899 and a few Symbios > controllers. The aic7899 seems to handle 16MB transfers. > Don't know about the Symbios chips. You should be fine with most any modern controller. The 7899 and Symbios controllers should be fine. > >> NOTE: While most of the kernel is based on 4.1-STABLE, I > >> believe the CAM subsystem and scsi_sa has been lifted > from > >> 4.3. (The behaviour is the same under 4.5) > > > >Sounds "interesting". :) > > > > We try to limit "changes", but every so often we need a fix > from a later release. And sometimes that involves back > porting a fair amount of code. I forget what the 4.1 CAM > problem was that caused us to pull in the 4.3 code. I know how it is. :) (Been there, done that, rather.) 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 5 21: 7:18 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 8D3DF37B405 for ; Tue, 5 Mar 2002 21:07:10 -0800 (PST) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.10.2+Sun/8.10.2) with ESMTP id g2656Sj01368; Tue, 5 Mar 2002 21:06:28 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id UAA15022; Tue, 5 Mar 2002 20:48:48 -0800 (PST) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id WAA18733; Tue, 5 Mar 2002 22:06:23 -0700 (MST) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id <1TZTW2SC>; Tue, 5 Mar 2002 22:06:25 -0700 Message-ID: From: "Long, Scott" To: "'Patrick Thomas'" , Tom Samplonius Cc: freebsd-scsi@freebsd.org Subject: RE: Dell PERC scrub / scrubbing question Date: Tue, 5 Mar 2002 22:06:24 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Specifically, what kind of controller is this? There were several sub-models of the Dell PERC2. Tom is correct, a scrub is when all blocks on a redundant array (0, 5, 10, 50, etc) are read and the mirror/parity data is recalculated and written. On some controllers, the array can be used while the scrub is in progress, but this slows down both the scrub operation and the I/O to the array. If the scrub completes but then starts again after a reboot it could be either a bug in the firmware on the card, or that the card may not be getting shut down correctly and the firmware is starting a scrub to verify that no data was lost. Please send me your dmesg output so I can determine if I can help you with some specific debugging procedures. Scott > -----Original Message----- > From: Patrick Thomas [mailto:root@utility.clubscholarship.com] > Sent: Tuesday, March 05, 2002 12:13 AM > To: Tom Samplonius > Cc: freebsd-scsi@freebsd.org > Subject: Re: Dell PERC scrub / scrubbing question > > > > These are mirrors I have created, though...RAID 1. Comments > ? (please :) > > --PT > > > > > When I created my mirrors originally with my Dell PERC 2 > controller, they > > > immediately started scrubbing. The BIOS told me not to > use them until > > > they were done scrubbing. Fair enough. > > > > Depends on what they mean by scrubbing. It usually takes > a long time to > > initialize a RAID5 volume, because the parity is created > for the first > > time. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 6 22:48:52 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by hub.freebsd.org (Postfix) with ESMTP id 493FA37B41F for ; Wed, 6 Mar 2002 22:48:49 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 16ir43-0001zq-00 for freebsd-scsi@freebsd.org; Wed, 6 Mar 2002 22:07:44 -0800 Date: Wed, 6 Mar 2002 22:07:42 -0800 (PST) From: Tom Samplonius To: freebsd-scsi@freebsd.org Subject: RAID motherboard compatibility Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've just discovered that the Mylex AccelRAID 352 is incompatible with an IBM eServer x342. We've have many of the previous models (x340) and they work fine, but a "Rehook int19h" option must be enabled in the BIOS, otherwise the RAID configuration can't be accessed during boot. However, IBM neglected to include the same option in the x342 BIOS, so the RAID configuration in accessible. We'll have to configure the card and disks in another system, and then move then over! Just so you are aware of how bizare this is, IBM bought Mylex over two years ago! Does anyone have ideas on whether Adaptec or American Megatrends cards would have the same problem in an x342? Both manufacturers are listed on the IBM site as being part of the IBM's certification program, but neither has certified any cards for the x342. I'm leaning towards the Adaptec 5400S. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 7 22:40:55 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 6760337B416 for ; Thu, 7 Mar 2002 22:40:54 -0800 (PST) Received: from utility.clubscholarship.com (user@utility.clubscholarship.com [198.78.70.175]) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g286d4r02522 for ; Thu, 7 Mar 2002 22:39:04 -0800 (PST) (envelope-from user@clubscholarship.com) Date: Thu, 7 Mar 2002 22:39:04 -0800 (PST) From: Patrick Thomas To: Subject: RE: Dell PERC scrub / scrubbing question Message-ID: <20020307223814.E93765-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org It turns out that the scrubbing process on mirrors starts from zero every time you _power off_ the machine. --PT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 7 23: 2:25 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 47E5937B41D for ; Thu, 7 Mar 2002 23:02:16 -0800 (PST) Received: from utility.clubscholarship.com (user@utility.clubscholarship.com [198.78.70.175]) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g2870Vr03042 for ; Thu, 7 Mar 2002 23:00:31 -0800 (PST) (envelope-from user@clubscholarship.com) Date: Thu, 7 Mar 2002 23:00:31 -0800 (PST) From: Patrick Thomas To: Subject: Dell PERC 2/QC only supples four containers to FreeBSD Message-ID: <20020307223905.P93765-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a Dell PERC 2/QC (the one with the four little micro connectors out the back...quad channel. I have 7 disks attached to channel 0 I have 4 disks attached to channel 1 --- I have made three RAID 1 mirror containers and left the 7th drive free as a standard volume on channel 0 I have made two RAID 1 mirror containers from the four drives on channel 1. So at this point, freeBSD should see 6 total disks. 5 mirror containers and one single volume. When FreeBSD 4.5-RELEASE cd installation boots, in the dmesg I indeed see all six entries: aacd0: on aac0 aacd0: 8677MN (17771264 sectors) aacd1: on aac0 aacd1: 17355MN (35544576 sectors) ... aacd5: on aac0 aacd5: 69998MB (143357184 sectors) So far so good - dmesg sees all six "disks". But, I go into custom installation, and choose the 'Partition' menu entry, and since I have multiple disks I am immediately shown the "Select Drives" screen - the problem is, there are only _four_ drives in this screen. The four drives are aacd0 - aacd3. They are not all from one channel either, one of them is from channel 1, and the other three are from channel 0. --- I have tried moving the cursor past the fourth entry on the list and have the list scroll, but there is nothing else there. It (partition menu of /stand/sysinstall) seems to make only four (and a somewhat random four) of my drives available to me to format, etc. Any thougts on this ? I am thinking that maybe the mfsroot.flp disk is built with only four aacdX /dev nodes ? If this is correct, I could make a new mfsroot.flp. I find it odd though that the four it does decide to show are spread across the two channels...Again, though, comments and/or suggestions appreciated. --PT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 7 23:42: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id E2F9E37B404 for ; Thu, 7 Mar 2002 23:42:03 -0800 (PST) Received: from utility.clubscholarship.com (user@utility.clubscholarship.com [198.78.70.175]) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g287eIr03784 for ; Thu, 7 Mar 2002 23:40:18 -0800 (PST) (envelope-from user@clubscholarship.com) Date: Thu, 7 Mar 2002 23:40:18 -0800 (PST) From: Patrick Thomas To: Subject: Dell PERC 2/QC only supples four containers to FreeBSD - MORE Message-ID: <20020307233746.M93765-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org one other note - I pressed 'alt-f2' while in sysinstall, and I saw these messages at the bottom of the screen: DEBUG: Unable to open disk aacd4 DEBUG: Unable to open disk aacd5 DEBUG: Unable to open disk cd0 Those are the two disks I am missing ... no idea why cd0 would not be able to be opened, since I am booting off of the only cdrom in the system and am at this point by virtue of using it successfully... So hopefully this information helps. I think this means perhaps it is not due to a lack of /dev nodes like I originally thought, because if so why would it be attempting to open them ? help / comments appreciated. --pt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 8 6:24:48 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id BBFB437B419 for ; Fri, 8 Mar 2002 06:24:44 -0800 (PST) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.10.2+Sun/8.10.2) with ESMTP id g28EObj01203; Fri, 8 Mar 2002 06:24:37 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id GAA23749; Fri, 8 Mar 2002 06:06:54 -0800 (PST) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id HAA10100; Fri, 8 Mar 2002 07:24:35 -0700 (MST) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id <1TZTWMMA>; Fri, 8 Mar 2002 07:24:35 -0700 Message-ID: From: "Long, Scott" To: "'Patrick Thomas'" , freebsd-scsi@freebsd.org Subject: RE: Dell PERC 2/QC only supples four containers to FreeBSD - MORE Date: Fri, 8 Mar 2002 07:24:34 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Patrick, This is just a guess, since I'm on the road and don't have my the sources to sysinstall handy. I imagine that sysinstall gets a list of storage devices from the kernel, then attempts to open each one. Only /dev/aacd0-3 exist by default, so aacd4-5 cannot be opened because no entries exist. If I'm right, then this might not be easy to work around, since I doubt that mknod is available to the 'Emergency holographic shell'. Maybe sysinstall can be taught how to create devices in this situation; I'll look into it later. The error about cd0 is most likely unrelated. Scott > -----Original Message----- > From: Patrick Thomas [mailto:user@utility.clubscholarship.com] > Sent: Friday, March 08, 2002 12:40 AM > To: freebsd-scsi@freebsd.org > Subject: Dell PERC 2/QC only supples four containers to FreeBSD - MORE > > > > one other note - I pressed 'alt-f2' while in sysinstall, and > I saw these > messages at the bottom of the screen: > > > DEBUG: Unable to open disk aacd4 > DEBUG: Unable to open disk aacd5 > DEBUG: Unable to open disk cd0 > > > Those are the two disks I am missing ... no idea why cd0 > would not be able > to be opened, since I am booting off of the only cdrom in the > system and > am at this point by virtue of using it successfully... > > So hopefully this information helps. I think this means > perhaps it is not > due to a lack of /dev nodes like I originally thought, > because if so why > would it be attempting to open them ? > > help / comments appreciated. > > --pt > > > 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 Fri Mar 8 11:27:56 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 907E637B405 for ; Fri, 8 Mar 2002 11:27:51 -0800 (PST) Received: from utility.clubscholarship.com (user@utility.clubscholarship.com [198.78.70.175]) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g28JPlr24334; Fri, 8 Mar 2002 11:25:47 -0800 (PST) (envelope-from user@clubscholarship.com) Date: Fri, 8 Mar 2002 11:25:47 -0800 (PST) From: Patrick Thomas To: "Long, Scott" Cc: Subject: RE: Dell PERC 2/QC only supples four containers to FreeBSD - MORE In-Reply-To: Message-ID: <20020308112252.J93765-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org mknod isnot available to the energency holographic shell, however it _is_ available to FIXIT. However, I think I will try installing the system with just the four disks, booting into a live system, mknod from a live system, then rerun /stand/sysinstall and run partition and label from the post-install configuration section. Do you think _all_ that needs to happen is that the nodes exist, or do you think further modifications (like recomppiling the kernel to support more than four aacX) ? I will be trying it within an hour or so and will post the results. --pt > > This is just a guess, since I'm on the road and don't have my the sources to > sysinstall handy. I imagine that sysinstall gets a list of storage devices > from the kernel, then attempts to open each one. Only /dev/aacd0-3 exist by > default, so aacd4-5 cannot be opened because no entries exist. If I'm > right, then this might not be easy to work around, since I doubt that mknod > is available to the 'Emergency holographic shell'. Maybe sysinstall can be > taught how to create devices in this situation; I'll look into it later. > The error about cd0 is most likely unrelated. > > Scott > > > -----Original Message----- > > From: Patrick Thomas [mailto:user@utility.clubscholarship.com] > > Sent: Friday, March 08, 2002 12:40 AM > > To: freebsd-scsi@freebsd.org > > Subject: Dell PERC 2/QC only supples four containers to FreeBSD - MORE > > > > > > > > one other note - I pressed 'alt-f2' while in sysinstall, and > > I saw these > > messages at the bottom of the screen: > > > > > > DEBUG: Unable to open disk aacd4 > > DEBUG: Unable to open disk aacd5 > > DEBUG: Unable to open disk cd0 > > > > > > Those are the two disks I am missing ... no idea why cd0 > > would not be able > > to be opened, since I am booting off of the only cdrom in the > > system and > > am at this point by virtue of using it successfully... > > > > So hopefully this information helps. I think this means > > perhaps it is not > > due to a lack of /dev nodes like I originally thought, > > because if so why > > would it be attempting to open them ? > > > > help / comments appreciated. > > > > --pt > > > > > > 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 Fri Mar 8 14:55:44 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id EFC8337B43B for ; Fri, 8 Mar 2002 14:55:23 -0800 (PST) Received: from utility.clubscholarship.com (user@utility.clubscholarship.com [198.78.70.175]) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g28MrSr27985; Fri, 8 Mar 2002 14:53:29 -0800 (PST) (envelope-from user@clubscholarship.com) Date: Fri, 8 Mar 2002 14:53:28 -0800 (PST) From: Patrick Thomas To: "Long, Scott" Cc: Subject: RE: Dell PERC 2/QC only supples four containers to FreeBSD - MORE In-Reply-To: Message-ID: <20020308144534.X27892-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ok, I installed my system with just the four drives available, and then booted it for the first time. Everything is fine. So now I go to /dev and: sh MAKEDEV aacd4 sh MAKEDEV aacd5 and it makes the devices just fine - as in _all_ of them - aacd4, aacd4[a-h], and aacd4s1[a-h] So that is perfect. Then I start /stand/sysinstall and fdisk can now see the additional two drives, I fdisk them, and then I label them and then I quit /stand/sysinstall. Then I edit /etc/fstab and put in entries: /dev/aacd4s1e /mnt4 ufs rw 2 2 and then I reboot. Here is the part that makes NO sense whatsoever. When I reboot, for each of the two drives, I get: Can't open /dev/aacd4s1e: Invalid argument /dev/aacd4s1e: CAN'T CHECK FILE SYSTEM /dev/aacd4s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Can't open /dev/aacd4s1e: Device not configured --- this confuses me because, of course, the device _is_ configured. Is this because I exited /stand/sysinstall without committing and didn't do the newfs operation ? or things like that ? If so, I can solve this two ways, but I need help as I don't know how to do these things: 1. somehow exit /stand/sysinstall in a way that does the newfs and things without actually installing anything... 2. do the newfs (or whatever I need to do) on the command line .. what commands do I need to run ? The good news is, I can use all six disks with the PERC raid controller... --PT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 8 15:12:41 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [62.212.105.185]) by hub.freebsd.org (Postfix) with ESMTP id A316737B405 for ; Fri, 8 Mar 2002 15:12:37 -0800 (PST) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 2FD502C3D1; Sat, 9 Mar 2002 00:12:32 +0100 (CET) Date: Sat, 9 Mar 2002 00:12:32 +0100 From: Thomas Quinot To: freebsd-scsi@freebsd.org Subject: ATAPI/CAM boot-time hang Message-ID: <20020309001232.A96693@melusine.cuivre.fr.eu.org> Reply-To: thomas@cuivre.fr.eu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-message-flag: WARNING! Using Outlook can damage your computer. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Some users of the ATAPI/CAM patches (available from http://www.cuivre.fr.eu.org/~thomas/atapicam/) have let me know that using the patch would hang their machine at boot time. From first investigation, it was determined that there was a problem with the inquiry commands that are performed during the CAM probe, and that disabling the PROBE_FULL_INQUIRY phase altogether resolved the problem for these users. Analysis of debug traces from the ATAPI/CAM code seems to indicate that, for these users, one of the ATAPI devices always responds with a UNIT ATTENTION condition to the 'full' INQUIRY CDB. In that case, the retry_count for the ccb is never decremented (per the following code in scsi_interpret_sense: case SSD_KEY_UNIT_ATTENTION: [...] if ((sense_flags & SF_RETRY_UA) != 0) { /* don't decrement retry count */ error = ERESTART; print_sense = FALSE; and so the kernel loops forever trying to send INQUIRY commands. There are now several options to address this issue: 1. consider that the device's behaviour is abnormal (ATAPI does always perform autosense, so UNIT ATTENTION should be cleared on the 2nd attempt) and create quirk entries for it; 2. decrement the retry count when receiving UNIT ATTENTION (but in that case, the probe machinery should not consider failure of full inquiry as an indication that the device has disappeared); 3. get rid of the full inquiry altogether (anything besides SHORT_INQUIRY_LENGTH is vendor-specific anyway -- do we actually use it?) 4. other solution? I'd like others' opinion on this problem... Thomas. -- Thomas.Quinot@Cuivre.FR.EU.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 9 15:19:41 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 4BF8637B419 for ; Sat, 9 Mar 2002 15:19:37 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g29NJJv59331; Sat, 9 Mar 2002 16:19:19 -0700 (MST) (envelope-from ken) Date: Sat, 9 Mar 2002 16:19:19 -0700 From: "Kenneth D. Merry" To: Thomas Quinot Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ATAPI/CAM boot-time hang Message-ID: <20020309161919.A59137@panzer.kdm.org> References: <20020309001232.A96693@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020309001232.A96693@melusine.cuivre.fr.eu.org>; from thomas@cuivre.fr.eu.org on Sat, Mar 09, 2002 at 12:12:32AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Mar 09, 2002 at 00:12:32 +0100, Thomas Quinot wrote: > Some users of the ATAPI/CAM patches (available from > http://www.cuivre.fr.eu.org/~thomas/atapicam/) have let me know that > using the patch would hang their machine at boot time. > > >From first investigation, it was determined that there was a problem > with the inquiry commands that are performed during the CAM probe, > and that disabling the PROBE_FULL_INQUIRY phase altogether resolved > the problem for these users. > > Analysis of debug traces from the ATAPI/CAM code seems to indicate > that, for these users, one of the ATAPI devices always responds > with a UNIT ATTENTION condition to the 'full' INQUIRY CDB. In that > case, the retry_count for the ccb is never decremented (per the > following code in scsi_interpret_sense: > case SSD_KEY_UNIT_ATTENTION: > [...] > if ((sense_flags & SF_RETRY_UA) != 0) { > /* don't decrement retry count */ > error = ERESTART; > print_sense = FALSE; > and so the kernel loops forever trying to send INQUIRY commands. That is illegal behavior (returning unit attention in response to an inquiry). An inquiry should only result in a check condition when the device can't fulfill the request. In this case, the device is sending back a unit attention, which has nothing to do with not being able to fulfill the request. The reason we set the SF_RETRY_UA flag is because unit attentions are expected conditions, and will be cleared as soon as they are reported. They aren't cleared by an inquiry, but then they aren't supposed to be reported in response to an inquiry. It's possible in -current that we might actually decrement the count for a unit attention, depending on what ASC/ASCQ are returned. > There are now several options to address this issue: > 1. consider that the device's behaviour is abnormal (ATAPI does > always perform autosense, so UNIT ATTENTION should be cleared > on the 2nd attempt) and create quirk entries for it; > 2. decrement the retry count when receiving UNIT ATTENTION (but in > that case, the probe machinery should not consider failure of > full inquiry as an indication that the device has disappeared); > 3. get rid of the full inquiry altogether (anything besides > SHORT_INQUIRY_LENGTH is vendor-specific anyway -- do we actually > use it?) Take a look at the scsi_inquiry_data structure in scsi_all.h. There are fields used to indicate the ability to do QAS, DT clocking, etc. At least the DT clocking bit is used in the transport layer, and the ses(4) driver needs some of the extended data as well. > 4. other solution? > > I'd like others' opinion on this problem... Well, it would help to find out what ASC/ASCQ are actually getting returned from the device. We know what the sense key is, but it would be useful to find out what ASC/ASCQ are reported. In -current, bootverbose (-v) should be sufficient to show the information. In -stable, change the 'print_sense = FALSE;' to 'print_sense = TRUE;' in the if statement you quoted above. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message