From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 15 10:00:37 2004 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 4A24B16A4CE; Sun, 15 Feb 2004 10:00:37 -0800 (PST) Received: from david.tolid.eu.org (213.237.119.114.adsl.rdo.worldonline.dk [213.237.119.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51CC643D1F; Sun, 15 Feb 2004 10:00:36 -0800 (PST) (envelope-from tolid@plab.ku.dk) Received: from david.tolid.eu.org (tolid@localhost [127.0.0.1]) by david.tolid.eu.org (8.12.10/8.12.9) with SMTP id i1FI0Xah045184; Sun, 15 Feb 2004 19:00:33 +0100 (CET) (envelope-from tolid@plab.ku.dk) Date: Sun, 15 Feb 2004 19:00:33 +0100 From: Anatoliy Dmytriyev To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Message-Id: <20040215190033.1a54db22@david.tolid.eu.org> Organization: The Protein Laboratory, University of Copenhagen X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: problems with Adaptec SCSI adapter and IBM harddrives 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: Sun, 15 Feb 2004 18:00:37 -0000 Hello, everybody! I need to install a scsi system on my 4.9 freebsd box and used the scsi card "Adaptec 29160 Ultra160 SCSI adapter" and external cabinet with the IBM drive: . After stratup FreeBSD detected Adaptec and hard drive, I did fdisk, label and newfs without any problems, but when I tried copy data on this scsi disk I got error messages: (da0:ahc0:0:6:0): SCB 0x3 - timed out >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahc0: Dumping Card State in Data-out phase, at SEQADDR 0x89 Card was paused ACCUM = 0x0, SINDEX = 0x2, DINDEX = 0x52, ARG_2 = 0xff HCNT = 0x0 SCBPTR = 0x1 SCSIPHASE[0x0] SCSISIGI[0x4] ERROR[0x0] SCSIBUSL[0x34] LASTPHASE[0x0] SCSISEQ[0x12] SBLKCTL[0x6] SCSIRATE[0x95] SEQCTL[0x10] SEQ_FLAGS[0x20] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x40] SSTAT3[0x0] SIMODE0[0x8] SIMODE1[0xac] SXFRCTL0[0x80] DFCNTRL[0x2c] DFSTATUS[0x89] STACK: 0x0 0x16b 0x63 0x89 SCB count = 20 Kernel NEXTQSCB = 12 Card NEXTQSCB = 14 QINFIFO entries: 14 15 0 16 17 18 19 1 2 4 5 6 7 8 9 13 Waiting Queue entries: Disconnected Queue entries: QOUTFIFO entries: Sequencer Free SCB List: 0 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Sequencer SCB Info: 0 SCB_CONTROL[0xe0] SCB_SCSIID[0x67] SCB_LUN[0x0] SCB_TAG[0xff] 1 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] SCB_TAG[0x3] 2 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 3 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 4 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 5 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 6 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 7 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 8 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 9 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 10 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 11 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 12 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 13 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 14 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 15 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 16 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 17 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 18 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 19 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 20 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 21 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 22 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 23 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 24 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 25 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 26 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 27 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 28 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 29 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 30 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] 31 SCB_CONTROL[0x0] SCB_SCSIID[0xff] SCB_LUN[0xff] SCB_TAG[0xff] Pending list: 13 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 9 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 8 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 7 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 6 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 5 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 4 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 2 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 1 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 19 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 18 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 17 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 16 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 0 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 15 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 14 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] 3 SCB_CONTROL[0x60] SCB_SCSIID[0x67] SCB_LUN[0x0] Kernel Free SCB list: 11 10 >>>>>>>>>>>>>>>>> sg[0] - Addr 0x6571000 : Length 4096 sg[1] - Addr 0x6972000 : Length 4096 sg[2] - Addr 0x6933000 : Length 4096 sg[3] - Addr 0x65b4000 : Length 4096 sg[4] - Addr 0x6775000 : Length 4096 sg[5] - Addr 0x6916000 : Length 4096 sg[6] - Addr 0x6b37000 : Length 4096 sg[7] - Addr 0x64f8000 : Length 4096 sg[8] - Addr 0x6df9000 : Length 4096 sg[9] - Addr 0x6d3a000 : Length 4096 sg[10] - Addr 0x6fdb000 : Length 4096 sg[11] - Addr 0x6d9c000 : Length 4096 sg[12] - Addr 0x6f1d000 : Length 4096 sg[13] - Addr 0x6d5e000 : Length 4096 sg[14] - Addr 0x6f7f000 : Length 4096 sg[15] - Addr 0x7080000 : Length 4096 (da0:ahc0:0:6:0): BDR message in message buffer (da0:ahc0:0:6:0): SCB 0x3 - timed out And many many times. I tried with other harddrive (the same model) and with card "Adaptec 2940 Ultra SCSI adapter" - the same result. Do you have any ideas: where is problems? I have not many experience with scsi devices and will appreciate for any help. Best regards, Anatoliy Dmytriyev -- Anatoliy Dmytriyev From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 16 15:15:59 2004 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 ED8CC16A4CE for ; Mon, 16 Feb 2004 15:15:59 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [216.52.22.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id E626A43D1D for ; Mon, 16 Feb 2004 15:15:59 -0800 (PST) (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 i1GNFxJ15150; Mon, 16 Feb 2004 15:15:59 -0800 Received: from [10.100.253.70] (aslan.btc.adaptec.com [10.100.253.70]) by redfish.adaptec.com (8.11.6/8.11.6) with ESMTP id i1GNFw812049; Mon, 16 Feb 2004 15:15:58 -0800 Date: Mon, 16 Feb 2004 23:22:42 -0700 From: "Justin T. Gibbs" To: Lukas Ertl , scsi@freebsd.org Message-ID: <1287100000.1076998962@aslan.btc.adaptec.com> In-Reply-To: <20040130174030.G635@korben.in.tern> References: <20040130174030.G635@korben.in.tern> X-Mailer: Mulberry/3.1.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: ahd(4) troubles 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: Mon, 16 Feb 2004 23:16:00 -0000 > Hi, > > I'm having trouble with an external RAID box that's connected to an > Adaptec 39320D adapter. Basically the setup works, but we get some > cryptic SCSI register dump on the console quite often. > > The kernel is a 5.2-CURRENT from Jan 19th (with SCHED_4BSD, if that > matters), and the adapter is probed as: This particular issue should be resolved by the checkin I made on February 4th. Please let me know if an updated driver does not resolve the problem for you. -- Justin From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 17 06:27:18 2004 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 44DCD16A4CE for ; Tue, 17 Feb 2004 06:27:18 -0800 (PST) Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B349743D1F for ; Tue, 17 Feb 2004 06:27:17 -0800 (PST) (envelope-from l.ertl@univie.ac.at) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) i1HERAIl1352094; Tue, 17 Feb 2004 15:27:12 +0100 Date: Tue, 17 Feb 2004 15:27:10 +0100 (CET) From: Lukas Ertl To: "Justin T. Gibbs" In-Reply-To: <1287100000.1076998962@aslan.btc.adaptec.com> Message-ID: <20040217152652.Y71950@pcle2.cc.univie.ac.at> References: <20040130174030.G635@korben.in.tern> <1287100000.1076998962@aslan.btc.adaptec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: mailbox 4244; Body=0 Fuz1=0 Fuz2=0 cc: scsi@freebsd.org Subject: Re: ahd(4) troubles 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, 17 Feb 2004 14:27:18 -0000 On Mon, 16 Feb 2004, Justin T. Gibbs wrote: > > I'm having trouble with an external RAID box that's connected to an > > Adaptec 39320D adapter. Basically the setup works, but we get some > > cryptic SCSI register dump on the console quite often. > > > > The kernel is a 5.2-CURRENT from Jan 19th (with SCHED_4BSD, if that > > matters), and the adapter is probed as: > > This particular issue should be resolved by the checkin I made on > February 4th. Please let me know if an updated driver does not > resolve the problem for you. Looks good so far, thanks! regards, le -- Lukas Ertl eMail: l.ertl@univie.ac.at UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 17 11:13:17 2004 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 4134316A4CE for ; Tue, 17 Feb 2004 11:13:17 -0800 (PST) Received: from tana.astro.umn.edu (tana.astro.umn.edu [128.101.221.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8753843D31 for ; Tue, 17 Feb 2004 11:13:12 -0800 (PST) (envelope-from carde@astro.umn.edu) Received: by tana.astro.umn.edu (Postfix, from userid 175) id 202FADF15; Tue, 17 Feb 2004 13:13:10 -0600 (CST) Date: Tue, 17 Feb 2004 13:13:09 -0600 From: kelley eicher To: scsi@freebsd.org Message-ID: <20040217191309.GA9123@astro.umn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: mylex X2000 - no raid disks 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, 17 Feb 2004 19:13:17 -0000 i have a mylex x2000 raid adapter that does some strange things under freebsd 4.8. during boot, the mly driver initializes the adapter but no raid disks appear even though they exist and function normally in the controller software. attempts to reboot the machine comes to a stop at: mly0: flushing cache... at which point the power button becomes useful. anyone have a similar experience or suggestion? thanx, -kelley -- >> kelley j eicher << the Bitkeeper of Gozer. >> Univ. of MN Astronomy Dept. << phone: (612) 626-2067 or (612) 624-3589 >> fax: (612) 626-2029 << office: 385 physics From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 17 13:58:22 2004 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 B406716A4CF for ; Tue, 17 Feb 2004 13:58:22 -0800 (PST) Received: from mx1.webspacesolutions.com (ns1.webspacesolutions.com [216.74.11.68]) by mx1.FreeBSD.org (Postfix) with SMTP id 8B99A43D2D for ; Tue, 17 Feb 2004 13:58:22 -0800 (PST) (envelope-from nick@webspacesolutions.com) Received: (qmail 29888 invoked by uid 507); 17 Feb 2004 21:58:22 -0000 Received: from nick@webspacesolutions.com by ns1.webspacesolutions.com by uid 504 with qmail-scanner-1.20rc1 (clamuko: 0.65. spamassassin: 2.55. Clear:RC:1:. Processed in 0.034965 secs); 17 Feb 2004 21:58:22 -0000 Received: from 24-205-247-185.ata-cres.charterpipeline.net (HELO beastie) (24.205.247.185) by mx1.webspacesolutions.com with SMTP; 17 Feb 2004 21:58:22 -0000 From: "Nick Twaddell" To: Date: Tue, 17 Feb 2004 13:58:30 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcP1oS2r/VzgTJynTOa6E7yRyWTdqg== X-Qmail-Scanner-Message-ID: <107705510263529883@ns1.webspacesolutions.com> Message-Id: <20040217215822.8B99A43D2D@mx1.FreeBSD.org> Subject: ips driver + ipssend 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, 17 Feb 2004 21:58:22 -0000 I saw a post a few months ago about this. Does anyone know if there will be an ipssend ported to freebsd for the ips raid driver? Right now there is no way to control the raid within freebsd I believe. Let me know if there are any other solutions. Nick Twaddell ---------------------------------------------------------------------------- -------- Nick Twaddell Web Space Solutions Ph: (805) 704-4038 Fx: (805) 434-2477 From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 17 14:45:15 2004 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 1A10916A4D1 for ; Tue, 17 Feb 2004 14:45:15 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id D7D7343D1F for ; Tue, 17 Feb 2004 14:45:14 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 64738 invoked by uid 1002); 17 Feb 2004 22:45:12 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 17 Feb 2004 22:45:12 -0000 Message-ID: <403298D5.4030002@freebsd.org> Date: Tue, 17 Feb 2004 15:42:29 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nick Twaddell References: <20040217215822.8B99A43D2D@mx1.FreeBSD.org> In-Reply-To: <20040217215822.8B99A43D2D@mx1.FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@FreeBSD.org Subject: Re: ips driver + ipssend 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, 17 Feb 2004 22:45:15 -0000 Nick Twaddell wrote: > I saw a post a few months ago about this. Does anyone know if there will be > an ipssend ported to freebsd for the ips raid driver? Right now there is no > way to control the raid within freebsd I believe. Let me know if there are > any other solutions. > > Nick Twaddell > No, there are no current plans to port ipssend. Porting is non-trivial since the code assumes that arrays are presented to the OS as SCSI devices rather than block devices. This also likely rules out running the linux tools in emulation mode. The only recourse that I can suggest is to call the Adaptec support hotline and complain. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 18 14:52:45 2004 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 4F82A16A4D2 for ; Wed, 18 Feb 2004 14:52:45 -0800 (PST) Received: from mail.bronskill.com (mail.bronskill.com [206.47.145.35]) by mx1.FreeBSD.org (Postfix) with SMTP id C369C43D2D for ; Wed, 18 Feb 2004 14:52:44 -0800 (PST) (envelope-from oliver@bronskill.com) Received: (qmail 25931 invoked from network); 18 Feb 2004 22:39:52 -0000 Received: from 206-47-145-36.ip.tor.radiant.net (HELO bronskill.com) (206.47.145.36) by mail.bronskill.com with SMTP; 18 Feb 2004 22:39:52 -0000 Message-ID: <4033ED82.4030405@bronskill.com> Date: Wed, 18 Feb 2004 17:56:02 -0500 From: Oliver Neubauer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Mylex DAC1180 booting problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: oliver@bronskill.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 22:52:45 -0000 Hello all, I'm having a tough time getting a new FreeBSD 5.2 installation to boot off of a RAID system drive (Mylex DAC1180, two RAID 5 system disks defined, 2G mode). Essentially, I have done a standard install, creating a FreeBSD slice on the smaller (5G) system drive (using the whole disk, non-dd mode) and even created a separate partition on that slice for /boot (200M). When I reboot the system, the boot screen says it can't find /boot or kernel. I suspect this is largely due to the fact that it seems to be looking on ad0a instead of mlxd0d since it's displaying something like 0:(ad,0)/boot I hate to sound like such a newb, but my attempts to change the loader's default is falling well short of producing any results. So I guess my direct questions are: How can I use the (horribly crippled, it seems) virtual shell from the installer to modify the boot loader's behavior via boot.conf (mounting the disk is the problem here). and/or How can I make it look for /boot on another device at boot time? Anyone have any helpful advice? Thanks Oliver From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 18 17:17:28 2004 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 D198416A4CE for ; Wed, 18 Feb 2004 17:17:28 -0800 (PST) Received: from twtpems2.wistron.com.tw (twtpems2.wistron.com.tw [210.63.110.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EE8F43D1F for ; Wed, 18 Feb 2004 17:17:28 -0800 (PST) (envelope-from jerry_ch_lee@wistron.com.tw) Received: from TWTPEDS1.WISTRON.COM.TW (unverified [210.63.109.150]) by twtpems2.wistron.com.tw (Content Technologies SMTPRS 4.3.10) with SMTP id for ; Thu, 19 Feb 2004 09:21:18 +0800 Received: by TWTPEDS1.WISTRON.COM.TW (Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 48256E3F.00071BE9; Thu, 19 Feb 2004 09:17:38 +0800 X-Lotus-FromDomain: WISTRON From: jerry_ch_lee@wistron.com.tw To: freebsd-scsi@freebsd.org Message-ID: <48256E3F.00071B1E.00@TWTPEDS1.WISTRON.COM.TW> Date: Thu, 19 Feb 2004 09:17:43 +0800 Mime-Version: 1.0 Content-type: text/plain; charset="us-ascii" Content-Disposition: inline Subject: scsi_target crashed when initiator is using LSI PCI-X Ultra320 SCSI card 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, 19 Feb 2004 01:17:28 -0000 Hi: Did anyone have such experience? My setup is: Initiator: PC with Windows 2000, LSI Ultra320 SCSI card Target: PC with FreeBSD 5.2, on-board Adaptec 7899W chip command on target: ./scsi_target 0:1:0 file When I rescan hardware on initiator, the Target's scsi_target program exit itself. Then I re-run scsi_target program again, and rescan hardware on initiator, then... Target crashed! ( I can't grab the log because it's not logged in messages) Any idea? Best regards, Jerry Lee Senior Engineer Broadband & Storage Wistron Corp. (TEL) 886-2-86911521 (CELL) 886-920894353 (EMAIL) jerry_ch_lee@wistron.com.tw (MSN) i_am_jhlee@hotmail.com From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 18 21:54:42 2004 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 ACFC516A4CF for ; Wed, 18 Feb 2004 21:54:42 -0800 (PST) Received: from web21105.mail.yahoo.com (web21105.mail.yahoo.com [216.136.227.107]) by mx1.FreeBSD.org (Postfix) with SMTP id A870843D1F for ; Wed, 18 Feb 2004 21:54:42 -0800 (PST) (envelope-from materribile@yahoo.com) Message-ID: <20040219055442.97978.qmail@web21105.mail.yahoo.com> Received: from [24.228.74.10] by web21105.mail.yahoo.com via HTTP; Wed, 18 Feb 2004 21:54:42 PST Date: Wed, 18 Feb 2004 21:54:42 -0800 (PST) From: Mark Terribile To: jerry_ch_lee@wistron.com.tw, freebsd-scsi@freebsd.org In-Reply-To: <48256E3F.00071B1E.00@TWTPEDS1.WISTRON.COM.TW> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: scsi_target crashed when initiator is using LSI PCI-X Ultra320 SCSI card 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, 19 Feb 2004 05:54:42 -0000 Jerry, > Initiator: PC with Windows 2000, LSI Ultra320 SCSI card > Target: PC with FreeBSD 5.2, on-board Adaptec 7899W chip > command on target: > ./scsi_target 0:1:0 file > > When I rescan hardware on initiator, the Target's scsi_target program exit > itself. Then I re-run scsi_target program again, and rescan hardware on >initiator, then... > > Target crashed! ( I can't grab the log because it's not logged in messages) My recent work was on a different setup (Linux initiator) but I found that when _anything_ changed (including the SCSI target emulator exiting or dying) I had to rescan on the initiator or else things would crash soon. Try rescanning the initiator after the emulator shuts down, before restarting it. And then you have to debug the target emulator. It took me a while to figure out how the confounded thing works. The key is the queues on which the transaction structs (I don't have it in front of me and do not recall their names, but there is one kind for ATIOs and one for CTIOs) are placed. They start out on one fixed queue, and are placed on another (different for ATIO and CTIO) when the struct is sent to the SCSI target layer via the write(2) on targN. When they are returned with work to do, the CTIOs are placed on queues linked to the ATIOs while the async read or write is underway. Side note in case you haven't been watching VERY closely: /dev/targ0, /dev/targ1, etc., are created WHEN YOU OPEN THEM in FreeBSD5.x; if they exist you can't open them because something else has the file open! Hope this helps. I'm curious about this one; I may have to play target to a MicroSoft initiator one of these days. Seems lots of people are making SCSI targets of themselves these days. Mark Terribile materribile@yahoo.com __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 19 01:11:40 2004 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 B37C916A4CE for ; Thu, 19 Feb 2004 01:11:40 -0800 (PST) Received: from twtpems3.wistron.com.tw (twtpems3.wistron.com.tw [210.63.110.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4890F43D1D for ; Thu, 19 Feb 2004 01:11:38 -0800 (PST) (envelope-from jerry_ch_lee@wistron.com.tw) Received: from TWTPEDS1.WISTRON.COM.TW (unverified [210.63.109.150]) by twtpems2.wistron.com.tw (Content Technologies SMTPRS 4.3.10) with SMTP id ; Thu, 19 Feb 2004 17:15:28 +0800 Received: by TWTPEDS1.WISTRON.COM.TW (Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 48256E3F.00328563; Thu, 19 Feb 2004 17:11:49 +0800 X-Lotus-FromDomain: WISTRON From: jerry_ch_lee@wistron.com.tw To: Mark Terribile Message-ID: <48256E3F.00328547.00@TWTPEDS1.WISTRON.COM.TW> Date: Thu, 19 Feb 2004 17:11:56 +0800 Mime-Version: 1.0 Content-type: text/plain; charset="us-ascii" Content-Disposition: inline cc: freebsd-scsi@freebsd.org Subject: Re: scsi_target crashed when initiator is using LSI PCI-X Ultra320 SCSI card 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, 19 Feb 2004 09:11:40 -0000 Hi Mark: But when the initiator is FreeBSD, it works pretty fine... I am not sure what is happening? I am sorry that I have something in my post... I am using Windows 2003 on initiator, not 2000. This still happens to me, even I used Adaptec 39320 card. Rescanning is not working... Best regards, Jerry Lee Senior Engineer Broadband & Storage Wistron Corp. (TEL) 886-2-86911521 (CELL) 886-920894353 (EMAIL) jerry_ch_lee@wistron.com.tw (MSN) i_am_jhlee@hotmail.com Mark Terribile on 2004/02/19 01:54:42 PM To: Jerry CH Lee/WHQ/Wistron@Wistron, freebsd-scsi@freebsd.org cc: Subject: Re: scsi_target crashed when initiator is using LSI PCI-X Ultra320 SCSI card This document is classified as Normal Jerry, > Target crashed! ( I can't grab the log because it's not logged in messages) My recent work was on a different setup (Linux initiator) but I found that when _anything_ changed (including the SCSI target emulator exiting or dying) I had to rescan on the initiator or else things would crash soon. Try rescanning the initiator after the emulator shuts down, before restarting it. And then you have to debug the target emulator. It took me a while to figure out how the confounded thing works. The key is the queues on which the transaction structs (I don't have it in front of me and do not recall their names, but there is one kind for ATIOs and one for CTIOs) are placed. They start out on one fixed queue, and are placed on another (different for ATIO and CTIO) when the struct is sent to the SCSI target layer via the write(2) on targN. When they are returned with work to do, the CTIOs are placed on queues linked to the ATIOs while the async read or write is underway. Side note in case you haven't been watching VERY closely: /dev/targ0, /dev/targ1, etc., are created WHEN YOU OPEN THEM in FreeBSD5.x; if they exist you can't open them because something else has the file open! Hope this helps. I'm curious about this one; I may have to play target to a MicroSoft initiator one of these days. Seems lots of people are making SCSI targets of themselves these days. Mark Terribile materribile@yahoo.com __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 19 06:52:18 2004 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 2364216A4CE for ; Thu, 19 Feb 2004 06:52:18 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas1tx.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD4B043D1F for ; Thu, 19 Feb 2004 06:52:17 -0800 (PST) (envelope-from chuck_tuffli@agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 71B617D4F; Thu, 19 Feb 2004 07:52:17 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 2861533; Thu, 19 Feb 2004 07:52:17 -0700 (MST) Received: from cre85086tuf.rose.agilent.com (cre85086tuf [130.30.174.150]) ESMTP id GAA12795; Thu, 19 Feb 2004 06:52:15 -0800 (PST) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id 54B3719E2AC; Thu, 19 Feb 2004 06:52:02 -0800 (PST) Date: Thu, 19 Feb 2004 06:52:02 -0800 From: Chuck Tuffli To: jerry_ch_lee@wistron.com.tw Message-ID: <20040219145201.GB88769@cre85086tuf.rose.agilent.com> References: <48256E3F.00071B1E.00@TWTPEDS1.WISTRON.COM.TW> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48256E3F.00071B1E.00@TWTPEDS1.WISTRON.COM.TW> User-Agent: Mutt/1.4i cc: freebsd-scsi@freebsd.org Subject: Re: scsi_target crashed when initiator is using LSI PCI-X Ultra320 SC SI card 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, 19 Feb 2004 14:52:18 -0000 I've been meaning to post a patch, but haven't gotten to it yet. The setup I tested with was similar (WinXP initiator and targ(4)). It appears that Windows sends a REPORT LUNS command which scsi_target doesn't support. In turn, the unsupported command causes scsi_target to abort. Here is a partial patch of the changes I made (this is against 4.9). Note that the CVS logs for scsi_target make some reference to a fix for REPORT LUNS, but I haven't looked into it at all. ---chuck --- ../st_49/scsi_cmds.c Tue Feb 18 14:07:10 2003 +++ scsi_cmds.c Tue Jan 20 12:40:31 2004 @@ -143,11 +143,14 @@ } if (last_cmd->cmd == ILLEGAL_CDB) { if (event != ATIO_WORK) { - warnx("no done func for %#x???", a_descr->cdb[0]); - abort(); + warnx("cdb %#x not handled (evt=%d)", a_descr->cdb[0], + event); + free_ccb((union ccb *)ctio); + return (1); } /* Not found, return illegal request */ - warnx("cdb %#x not handled", a_descr->cdb[0]); + if (debug) + warnx("cdb %#x not handled (evt=%d)", a_descr->cdb[0], event); tcmd_illegal_req(atio, ctio); send_ccb((union ccb *)ctio, /*priority*/1); return (0); @@ -245,12 +248,11 @@ /* Fill out the supplied CTIO */ if (ctio != NULL) { - /* No autosense yet bcopy(sense, &ctio->sense_data, sizeof(*sense)); - ctio->sense_len = sizeof(*sense); XXX - */ + ctio->sense_len = sizeof(*sense); + ctio->ccb_h.flags &= ~CAM_DIR_MASK; - ctio->ccb_h.flags |= CAM_DIR_NONE | /* CAM_SEND_SENSE | */ + ctio->ccb_h.flags |= CAM_DIR_NONE | CAM_SEND_SENSE | CAM_SEND_STATUS; ctio->dxfer_len = 0; ctio->scsi_status = SCSI_STATUS_CHECK_COND; @@ -313,6 +315,10 @@ } else { bcopy(&inq_data, ctio->data_ptr, sizeof(inq_data)); ctio->dxfer_len = inq_data.additional_length + 4; + + /* calculate the residual */ + ctio->resid = ctio->dxfer_len - SCSI_CDB6_LEN(inq->length); + ctio->dxfer_len = min(ctio->dxfer_len, On Wed, Feb 18, 2004 at 08:17:43PM -0500, jerry_ch_lee@wistron.com.tw wrote: > > > > Hi: > > Did anyone have such experience? > My setup is: > > Initiator: PC with Windows 2000, LSI Ultra320 SCSI card > Target: PC with FreeBSD 5.2, on-board Adaptec 7899W chip > command on target: > ./scsi_target 0:1:0 file > > When I rescan hardware on initiator, the Target's scsi_target program > exit > itself. > Then I re-run scsi_target program again, and rescan hardware on > initiator, > then... > > Target crashed! ( I can't grab the log because it's not logged in > messages) > > Any idea? > > Best regards, > > Jerry Lee > Senior Engineer > Broadband & Storage > Wistron Corp. > (TEL) 886-2-86911521 > (CELL) 886-920894353 > (EMAIL) jerry_ch_lee@wistron.com.tw > (MSN) i_am_jhlee@hotmail.com > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" -- Chuck Tuffli Agilent Technologies, Storage Area Networking From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 19 17:21:30 2004 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 0061C16A4CE for ; Thu, 19 Feb 2004 17:21:30 -0800 (PST) Received: from bsd.ite.com.tw (bsd.ite.com.tw [210.208.198.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2668943D31 for ; Thu, 19 Feb 2004 17:21:29 -0800 (PST) (envelope-from Mark.Lu@ite.com.tw) Received: from itemail1.internal.ite.com.tw ([192.168.35.13]) by bsd.ite.com.tw (8.8.8/8.8.8) with ESMTP id JAA05032 for ; Fri, 20 Feb 2004 09:29:08 +0800 (CST) (envelope-from Mark.Lu@ite.com.tw) From: Mark.Lu@ite.com.tw content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6524.0 Date: Fri, 20 Feb 2004 09:20:55 +0800 Message-ID: <884B07FD576C3F49938D233F0E0A2B00AB1C8B@itemail1.internal.ite.com.tw> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: The IT8212 ATA133 PCI RAID controller problem Thread-Index: AcP3T8g3A+pW0mGrSTqITTANLEnaTw== Sensitivity: Private To: Subject: The IT8212 ATA133 PCI RAID controller problem 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: Fri, 20 Feb 2004 01:21:30 -0000 Hi! Recently, I ported the IT8212 Linux driver to FreeBSD CAM SCSI device = driver. But I have a strange problem. When copying data from IT8212 disk to = IT8212 disk then diff the contents, it's fine. But when copying data from = onboard disk or onboard CD-ROM to IT8212 disk then diff the contents, some data will be = different. That's why I don't understand because the process is the same and no any = errors is showed. Does anyone have the same experience? If anyone wants to review the FreeBSD source code, it will be wonderful = and thanks! Best regards Mark e-mail: tlclu@ms1.hinet.net or mark.lu@ite.com.tw From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 19 22:41:26 2004 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 F359116A4CE for ; Thu, 19 Feb 2004 22:41:25 -0800 (PST) Received: from twtpems2.wistron.com.tw (twtpems2.wistron.com.tw [210.63.110.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D50043D1D for ; Thu, 19 Feb 2004 22:41:25 -0800 (PST) (envelope-from jerry_ch_lee@wistron.com.tw) Received: from TWTPEDS1.WISTRON.COM.TW (unverified [210.63.109.150]) by twtpems2.wistron.com.tw (Content Technologies SMTPRS 4.3.10) with SMTP id ; Fri, 20 Feb 2004 13:55:11 +0800 Received: by TWTPEDS1.WISTRON.COM.TW (Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 48256E40.0020303A; Fri, 20 Feb 2004 13:51:34 +0800 X-Lotus-FromDomain: WISTRON From: jerry_ch_lee@wistron.com.tw To: Chuck Tuffli Message-ID: <48256E40.00202F5A.00@TWTPEDS1.WISTRON.COM.TW> Date: Fri, 20 Feb 2004 13:51:39 +0800 Mime-Version: 1.0 Content-type: text/plain; charset="us-ascii" Content-Disposition: inline cc: freebsd-scsi@freebsd.org Subject: Re: scsi_target crashed when initiator is using LSI PCI-X Ultra320SC SI card 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: Fri, 20 Feb 2004 06:41:26 -0000 Hi Chuck: It works! Great job! Thanks! Best regards, Jerry Lee Senior Engineer Broadband & Storage Wistron Corp. (TEL) 886-2-86911521 (CELL) 886-920894353 (EMAIL) jerry_ch_lee@wistron.com.tw (MSN) i_am_jhlee@hotmail.com Chuck Tuffli on 2004/02/19 10:52:02 PM To: Jerry CH Lee/WHQ/Wistron@Wistron cc: freebsd-scsi@freebsd.org Subject: Re: scsi_target crashed when initiator is using LSI PCI-X Ultra320 SC SI card This document is classified as Normal I've been meaning to post a patch, but haven't gotten to it yet. The setup I tested with was similar (WinXP initiator and targ(4)). It appears that Windows sends a REPORT LUNS command which scsi_target doesn't support. In turn, the unsupported command causes scsi_target to abort. Here is a partial patch of the changes I made (this is against 4.9). Note that the CVS logs for scsi_target make some reference to a fix for REPORT LUNS, but I haven't looked into it at all. ---chuck --- ../st_49/scsi_cmds.c Tue Feb 18 14:07:10 2003 +++ scsi_cmds.c Tue Jan 20 12:40:31 2004 @@ -143,11 +143,14 @@ } if (last_cmd->cmd == ILLEGAL_CDB) { if (event != ATIO_WORK) { - warnx("no done func for %#x???", a_descr->cdb[0]); - abort(); + warnx("cdb %#x not handled (evt=%d)", a_descr->cdb[0], + event); + free_ccb((union ccb *)ctio); + return (1); } /* Not found, return illegal request */ - warnx("cdb %#x not handled", a_descr->cdb[0]); + if (debug) + warnx("cdb %#x not handled (evt=%d)", a_descr->cdb[0], event); tcmd_illegal_req(atio, ctio); send_ccb((union ccb *)ctio, /*priority*/1); return (0); @@ -245,12 +248,11 @@ /* Fill out the supplied CTIO */ if (ctio != NULL) { - /* No autosense yet bcopy(sense, &ctio->sense_data, sizeof(*sense)); - ctio->sense_len = sizeof(*sense); XXX - */ + ctio->sense_len = sizeof(*sense); + ctio->ccb_h.flags &= ~CAM_DIR_MASK; - ctio->ccb_h.flags |= CAM_DIR_NONE | /* CAM_SEND_SENSE | */ + ctio->ccb_h.flags |= CAM_DIR_NONE | CAM_SEND_SENSE | CAM_SEND_STATUS; ctio->dxfer_len = 0; ctio->scsi_status = SCSI_STATUS_CHECK_COND; @@ -313,6 +315,10 @@ } else { bcopy(&inq_data, ctio->data_ptr, sizeof(inq_data)); ctio->dxfer_len = inq_data.additional_length + 4; + + /* calculate the residual */ + ctio->resid = ctio->dxfer_len - SCSI_CDB6_LEN(inq->length); + ctio->dxfer_len = min(ctio->dxfer_len, On Wed, Feb 18, 2004 at 08:17:43PM -0500, jerry_ch_lee@wistron.com.tw wrote: > > > > Hi: > > Did anyone have such experience? > My setup is: > > Initiator: PC with Windows 2000, LSI Ultra320 SCSI card > Target: PC with FreeBSD 5.2, on-board Adaptec 7899W chip > command on target: > ./scsi_target 0:1:0 file > > When I rescan hardware on initiator, the Target's scsi_target program > exit > itself. > Then I re-run scsi_target program again, and rescan hardware on > initiator, > then... > > Target crashed! ( I can't grab the log because it's not logged in > messages) > > Any idea? > > Best regards, > > Jerry Lee > Senior Engineer > Broadband & Storage > Wistron Corp. > (TEL) 886-2-86911521 > (CELL) 886-920894353 > (EMAIL) jerry_ch_lee@wistron.com.tw > (MSN) i_am_jhlee@hotmail.com > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" -- Chuck Tuffli Agilent Technologies, Storage Area Networking From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 19 23:52:47 2004 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 40F3416A4CE for ; Thu, 19 Feb 2004 23:52:47 -0800 (PST) Received: from twtpems2.wistron.com.tw (twtpems2.wistron.com.tw [210.63.110.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A0DD43D1D for ; Thu, 19 Feb 2004 23:52:46 -0800 (PST) (envelope-from jerry_ch_lee@wistron.com.tw) Received: from TWTPEDS1.WISTRON.COM.TW (unverified [210.63.109.150]) by twtpems2.wistron.com.tw (Content Technologies SMTPRS 4.3.10) with SMTP id for ; Fri, 20 Feb 2004 15:56:39 +0800 Received: by TWTPEDS1.WISTRON.COM.TW (Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 48256E40.002AE8D2; Fri, 20 Feb 2004 15:48:41 +0800 X-Lotus-FromDomain: WISTRON From: jerry_ch_lee@wistron.com.tw To: freebsd-scsi@freebsd.org Message-ID: <48256E40.002AD880.00@TWTPEDS1.WISTRON.COM.TW> Date: Fri, 20 Feb 2004 15:47:48 +0800 Mime-Version: 1.0 Content-type: text/plain; charset="us-ascii" Content-Disposition: inline cc: andy_chen@wistron.com.tw Subject: scsi_target tagged queueing not working 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: Fri, 20 Feb 2004 07:52:47 -0000 Hi All: I am testing scsi_target ok with Chuck's patch (please see my latest post - http://lists.freebsd.org/pipermail/freebsd-scsi/2004-February/000997.html), it's cool! But I tried to enable tagged queuing by scsi_target command line like following line, the initiator (Windows 2003) can't detect it, no matter how many times I tried. Does anyone have this experience? This also happens before I used Chuck's patch. ./scsi_target -T 0:1:0 testfile As I know, this should be emulated ok by scsi_target usermode, isn't it? My environment: Initiator: PC with Windows 2003 Enterprise Edition, Adaptec 29160 SCSI card Target: PC with FreeBSD 5.2, On-board Adaptec 7899W chip. Best regards, Jerry Lee Senior Engineer Broadband & Storage Wistron Corp. (TEL) 886-2-86911521 (CELL) 886-920894353 (EMAIL) jerry_ch_lee@wistron.com.tw (MSN) i_am_jhlee@hotmail.com From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 20 07:22:11 2004 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 4108C16A4CE for ; Fri, 20 Feb 2004 07:22:11 -0800 (PST) Received: from tx1.oucs.ox.ac.uk (tx1.oucs.ox.ac.uk [129.67.1.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1920043D1F for ; Fri, 20 Feb 2004 07:22:11 -0800 (PST) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from scan1.oucs.ox.ac.uk ([129.67.1.166] helo=localhost) by tx1.oucs.ox.ac.uk with esmtp (Exim 4.24) id 1AuCTi-000810-Gy for scsi@freebsd.org; Fri, 20 Feb 2004 15:22:10 +0000 Received: from rx1.oucs.ox.ac.uk ([129.67.1.165]) by localhost (scan1.oucs.ox.ac.uk [129.67.1.166]) (amavisd-new, port 25) with ESMTP id 30747-02 for ; Fri, 20 Feb 2004 15:22:10 +0000 (GMT) Received: from gateway.wadham.ox.ac.uk ([163.1.161.253]) by rx1.oucs.ox.ac.uk with smtp (Exim 4.24) id 1AuCTi-00080t-3W for scsi@freebsd.org; Fri, 20 Feb 2004 15:22:10 +0000 Received: (qmail 14116 invoked by uid 0); 20 Feb 2004 15:22:10 -0000 Received: from colin.percival@wadham.ox.ac.uk by gateway by uid 71 with qmail-scanner-1.16 (sweep: 2.14/3.71. spamassassin: 2.53. Clear:. Processed in 1.73765 secs); 20 Feb 2004 15:22:10 -0000 X-Qmail-Scanner-Mail-From: colin.percival@wadham.ox.ac.uk via gateway X-Qmail-Scanner: 1.16 (Clear:. Processed in 1.73765 secs) Received: from dhcp1131.wadham.ox.ac.uk (HELO piii600.wadham.ox.ac.uk) (163.1.161.131) by gateway.wadham.ox.ac.uk with SMTP; 20 Feb 2004 15:22:08 -0000 Message-Id: <6.0.1.1.1.20040220151626.03b34568@imap.sfu.ca> X-Sender: cperciva@imap.sfu.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Fri, 20 Feb 2004 15:22:04 +0000 To: rwatson@freebsd.org, scsi@freebsd.org From: Colin Percival Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: commit approval 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: Fri, 20 Feb 2004 15:22:11 -0000 Dear mentor and scsi maintainers, Is the following commit ok? Colin Percival Log: Check that periph is non-NULL before dereferencing it. Reported by: "Ted Unangst" Index: src/sys/cam/scsi/scsi_da.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v retrieving revision 1.163 diff -u -r1.163 scsi_da.c --- src/sys/cam/scsi/scsi_da.c 18 Feb 2004 21:36:50 -0000 1.163 +++ src/sys/cam/scsi/scsi_da.c 20 Feb 2004 14:59:52 -0000 @@ -464,11 +464,11 @@ s = splsoftcam(); periph = (struct cam_periph *)dp->d_drv1; - unit = periph->unit_number; if (periph == NULL) { splx(s); return (ENXIO); } + unit = periph->unit_number; softc = (struct da_softc *)periph->softc; From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 20 07:32:15 2004 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 7A90A16A4CE; Fri, 20 Feb 2004 07:32:15 -0800 (PST) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id C169143D2D; Fri, 20 Feb 2004 07:32:14 -0800 (PST) (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 i1KFWELX016918; Fri, 20 Feb 2004 08:32:14 -0700 (MST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i1KFWDeb016917; Fri, 20 Feb 2004 08:32:13 -0700 (MST) (envelope-from ken) Date: Fri, 20 Feb 2004 08:32:13 -0700 From: "Kenneth D. Merry" To: Colin Percival Message-ID: <20040220153213.GA16894@panzer.kdm.org> References: <6.0.1.1.1.20040220151626.03b34568@imap.sfu.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.1.1.1.20040220151626.03b34568@imap.sfu.ca> User-Agent: Mutt/1.4.1i cc: rwatson@freebsd.org cc: scsi@freebsd.org Subject: Re: commit approval 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: Fri, 20 Feb 2004 15:32:15 -0000 On Fri, Feb 20, 2004 at 15:22:04 +0000, Colin Percival wrote: > Dear mentor and scsi maintainers, > Is the following commit ok? > > Colin Percival > > Log: > Check that periph is non-NULL before dereferencing it. > > Reported by: "Ted Unangst" > > Index: src/sys/cam/scsi/scsi_da.c > =================================================================== > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v > retrieving revision 1.163 > diff -u -r1.163 scsi_da.c > --- src/sys/cam/scsi/scsi_da.c 18 Feb 2004 21:36:50 -0000 1.163 > +++ src/sys/cam/scsi/scsi_da.c 20 Feb 2004 14:59:52 -0000 > @@ -464,11 +464,11 @@ > > s = splsoftcam(); > periph = (struct cam_periph *)dp->d_drv1; > - unit = periph->unit_number; > if (periph == NULL) { > splx(s); > return (ENXIO); > } > + unit = periph->unit_number; > > softc = (struct da_softc *)periph->softc; > Looks fine, feel free to commit. Ken -- Kenneth Merry ken@FreeBSD.org From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 20 23:58:04 2004 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 E307916A4CE; Fri, 20 Feb 2004 23:58:04 -0800 (PST) Received: from mail005.syd.optusnet.com.au (mail005.syd.optusnet.com.au [211.29.132.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B179C43D1F; Fri, 20 Feb 2004 23:58:03 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i1L7w1g30281; Sat, 21 Feb 2004 18:58:02 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id 0B7FD3DA; Sat, 21 Feb 2004 18:58:00 +1100 (EST) Date: Sat, 21 Feb 2004 18:58:00 +1100 From: Tony Frank To: freebsd-scsi@freebsd.org Message-ID: <20040221075800.GC98919@marvin.home.local> References: <20040221034749.GA98919@marvin.home.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040221034749.GA98919@marvin.home.local> User-Agent: Mutt/1.4.2.1i cc: FreeBSD-questions@freebsd.org Subject: Re: ahc + vinum raid5 deadlocks? 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: Sat, 21 Feb 2004 07:58:05 -0000 Hi, Cross posting to -scsi as it seems maybe related to my scsi setup. At least, the problems currently only appear when the scsi parts are in use. On Sat, Feb 21, 2004 at 02:47:49PM +1100, Tony Frank wrote: > Refer earlier thread on -stable for more background. > > 4.9-STABLE (cvsup 20th Feb) > Kernel was compiled with DDB, INVARIANTS, DIAGNOSTICS. > All options removed from /etc/make.conf except 'NOPROFILE=TRUE' > > I get the following on the console before system freezes: > ahc0: WARNING no command for scb 14 (cmdcmplt) > QOUTPOS = 44 This occured while doing majority of i/o to vinum raid5 volume. Since that time I have removed the vinum raid5 configuration and am using the disks directly - ufs mounted on /dev/da0s1h. When performing the same load benchmark I have received two separate panic's: First panic occurs due to KASSERT in ffs_read, refer: http://fxr.watson.org/fxr/source//ufs/ufs/ufs_readwrite.c?v=RELENG4#L316 %%%% (da0:ahc0:0:0:0): tagged openings now 40 (da1:ahc0:0:1:0): tagged openings now 40 (da2:ahc0:0:2:0): tagged openings now 40 (da3:ahc0:0:3:0): tagged openings now 40 Feb 21 15:48:16 raider su: tony to root on /dev/ttypc panic: bp->b_resid != 0 syncing disks... Stopped at siointr1+0x102: movl $0,brk_state2.757 db> trace siointr1(c0f98000,ccdc6c64,c027d546,c0f98000,10) at siointr1+0x102 siointr(c0f98000,10,0,0,0) at siointr+0xb Xfastintr4(c1090800,1000040,600,20002,ccd54300) at Xfastintr4+0x16 lockmgr(c1090800,1030002,ccd5436c,c032c7a0,ccdc6cac) at lockmgr+0x1fc vop_stdlock(ccdc6cc4,ccdc6cd4,c01bb269,ccdc6cc4,0) at vop_stdlock+0x20 ufs_vnoperatespec(ccdc6cc4) at ufs_vnoperatespec+0x15 vn_lock(ccd54300,20002,c032c7a0,c1129000,0) at vn_lock+0x71 ffs_sync(c1129000,2,c0b2d600,c032c7a0,c1129000) at ffs_sync+0x17f sync(c032c7a0,0,c02b9660,c02d6048,100) at sync+0x63 boot(100,0,0,ccdc6de0,c02482a2) at boot+0x8a panic(c02d6048,ccf5cbc0,5b,ccd8f000,400) at panic+0x79 ffs_read(ccdc6df4,0,ccdc6ea8,c02ec1e0,ccf5cbc0) at ffs_read+0x37a ufs_readlink(ccdc6e38,ccdc6e68,c01b1c8a,ccdc6e38,c7f7bee0) at ufs_readlink+0x6b ufs_vnoperate(ccdc6e38,c7f7bee0,c7f7bee0,ccdc6f80,c7f7bee0) at ufs_vnoperate+0x15 namei(ccdc6e80,c7f7bee0,2,ccdc6f80,8137400) at namei+0x302 stat(c7f7bee0,ccdc6f80,bfbe7810,bfbe8298,bfbea49c) at stat+0x41 syscall2(c027002f,2f,2f,bfbea49c,bfbe8298) at syscall2+0x209 Xint0x80_syscall() at Xint0x80_syscall+0x25 db> %%%% I have a core from this panic saved. 'trace' is about the extent of my ddb skills at the moment though. Checking the archives a similar problem was seen ~6months ago with particular SCSI disk and having too high tags value. Refer: http://docs.freebsd.org/cgi/mid.cgi?FE045D4D9F7AED4CBFF1B3B813C8533702741FEA >From what I can see, the ahc driver is forcing a max of 40 tags. The SCSI hardware is fairly old but was working without problems in the old system (Win based) Second panic occurs in ffs_softdep, refer: http://fxr.watson.org/fxr/source//ufs/ffs/ffs_softdep.c?v=RELENG4#L3590 %%%% Feb 21 17:16:30 raider su: tony to root on /dev/ttyp8 (da1:ahc0:0:1:0): tagged openings now 40 Feb 21 17:21:29 raider su: tony to root on /dev/ttyp3 (da3:ahc0:0:3:0): tagged openings now 40 (da2:ahc0:0:2:0): tagged openings now 40 panic: handle_written_inodeblock: live inodedep syncing disks... Stopped at siointr1+0x102: movl $0,brk_state2.757 db> trace siointr1(c0f98000,ccf6bba0,c027d546,c0f98000,10) at siointr1+0x102 siointr(c0f98000,10,0,8,68c040) at siointr+0xb Xfastintr4(c389c20c,10,c02be0a4,0) at Xfastintr4+0x16 biowait(c389c20c,c106b800,c11d1900,2,c02ec760) at biowait+0x37 bread(ccaaba00,18c040,2000,0,ccf6bc14) at bread+0xb2 ffs_update(ccd51c00,0,68c040,ccd51c00,ccf33580) at ffs_update+0xba ffs_fsync(ccf6bc78) at ffs_fsync+0x358 ffs_sync(c1069c00,2,c0b2d600,c032c7a0,c1069c00) at ffs_sync+0xdb sync(c032c7a0,0,c02b9660,c02d56e0,100) at sync+0x63 boot(100,0,c127bb00,ccf6bd18,c024416a) at boot+0x8a panic(c02d56e0,1,c11a5c80,c38d6178,0) at panic+0x79 handle_written_inodeblock(c11a5c80,c38d6150) at handle_written_inodeblock+0x30e softdep_disk_write_complete(c38d6150) at softdep_disk_write_complete+0x6a biodone(c38d6150,1,68c040,c10efa48,c38d6150) at biodone+0x121 complete_rqe(c10efa20,0,c1028c00,f76,c1028d3c) at complete_rqe+0x651 biodone(c10efa20,c1028cb8,c10efa20,c0146d58,c16caac0) at biodone+0xf5 ad_interrupt(c16caac0,c032b7d4,ccf6be38,c0182482,c0fa7900) at ad_interrupt+0x3e7 ata_intr(c0fa7900,c16ccdc0,ccf6be8c,c027e4c2,c032b7d4) at ata_intr+0xd8 add_interrupt_randomness(c032b7d4,0,10,c3870010,c01a0010) at add_interrupt_rando mness+0xe Xresume15() at Xresume15+0x2b --- interrupt, eip = 0xc01ab6e5, esp = 0xccf6be80, ebp = 0xccf6be8c --- bwillwrite(c16ccdc0,ccf6bf80,cce7b2a0,0,0) at bwillwrite+0x75 dofilewrite(cce7b2a0,c16ccdc0,a,824a00c,f76) at dofilewrite+0xa2 write(cce7b2a0,ccf6bf80,824a00c,bfbff7e0,bfbff800) at write+0x36 syscall2(bfbf002f,bfbf002f,822002f,bfbff800,bfbff7e0) at syscall2+0x209 Xint0x80_syscall() at Xint0x80_syscall+0x25 db> %%%% My searches show a few hits for -current and some old items from -stable. Nothing jumps out at me as a possible solution? This trace seems to suggest the problem may have been on the IDE disk? Again the core has been saved so given suitable directions I can do something with it. > Hardware is currently Adaptec AHA-2940W S71 (F/w 1.19S8) > Same issues occured with Adaptec AHA-2940UW/B (F/w 1.32S8) > I have 4 x 4G IBM SCSI disks on the single internal 68-pin connector. > Connections are good & termination is correct > The 4 disks are combined into a single vinum raid5 plex. > System is well ventilated and cool to the touch. > Pentium 2 200Mhz, 128mb SDRAM, Asus P2V m/b. > > Currently takes ~2 hours of solid activity to trigger the issue. These problems are occuring with load after about 30-50 mins of solid activity. a 'plain' "make -j4 buildworld buildkernel" completes ok if it runs by itself without the extra load of my test bench. > My 'test bench': > Copying files over NFSv3/udp to vinum raid5 volume via cp & tar > + make -j4 buildworld > + Copying large dir trees (/usr/ports, /usr/obj, /usr/src) > + cvsuping second copy of /usr/src > + extracting tar archive of /usr/obj Ideas are welcome, Tony From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 21 00:09:27 2004 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 2FFB716A4CE for ; Sat, 21 Feb 2004 00:09:27 -0800 (PST) Received: from mx1.webspacesolutions.com (ns1.webspacesolutions.com [216.74.11.68]) by mx1.FreeBSD.org (Postfix) with SMTP id 075DE43D2F for ; Sat, 21 Feb 2004 00:09:27 -0800 (PST) (envelope-from nick@webspacesolutions.com) Received: (qmail 4953 invoked by uid 507); 21 Feb 2004 08:09:26 -0000 Received: from nick@webspacesolutions.com by ns1.webspacesolutions.com by uid 504 with qmail-scanner-1.20rc1 (clamuko: 0.65. spamassassin: 2.55. Clear:RC:1:. Processed in 0.058985 secs); 21 Feb 2004 08:09:26 -0000 Received: from 24-205-247-185.ata-cres.charterpipeline.net (HELO beastie) (24.205.247.185) by mx1.webspacesolutions.com with SMTP; 21 Feb 2004 08:09:26 -0000 From: "Nick Twaddell" To: Date: Sat, 21 Feb 2004 00:09:27 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcP4UgZNwIDQuzYvTi6J0SbhXy99aw== X-Qmail-Scanner-Message-ID: <10773509666354940@ns1.webspacesolutions.com> Message-Id: <20040221080927.075DE43D2F@mx1.FreeBSD.org> Subject: raid controllers 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: Sat, 21 Feb 2004 08:09:27 -0000 So who makes a good Raid controller that is fully supported in FreeBSD and I can manage it from the command line? Since it doesent look like we will be seeing an ipssend in freebsd. Nick ---------------------------------------------------------------------------- -------- Nick Twaddell Web Space Solutions Ph: (805) 704-4038 Fx: (805) 434-2477 From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 21 07:51:55 2004 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 19EF616A4CE for ; Sat, 21 Feb 2004 07:51:55 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id D74E143D1F for ; Sat, 21 Feb 2004 07:51:54 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 720F5341D7; Sat, 21 Feb 2004 11:47:00 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 6EEC3341A6; Sat, 21 Feb 2004 11:47:00 -0400 (AST) Date: Sat, 21 Feb 2004 11:47:00 -0400 (AST) From: "Marc G. Fournier" To: Nick Twaddell In-Reply-To: <20040221080927.075DE43D2F@mx1.FreeBSD.org> Message-ID: <20040221114502.N9391@ganymede.hub.org> References: <20040221080927.075DE43D2F@mx1.FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: raid controllers 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: Sat, 21 Feb 2004 15:51:55 -0000 On Sat, 21 Feb 2004, Nick Twaddell wrote: > So who makes a good Raid controller that is fully supported in FreeBSD and I > can manage it from the command line? Since it doesent look like we will be > seeing an ipssend in freebsd. Adaptec does ... and there is aacli in ports to manage it Intel does ... and there is an iir cli also, but the URL to it eludes me right now ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 21 08:01:45 2004 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 4A38616A4CE for ; Sat, 21 Feb 2004 08:01:45 -0800 (PST) Received: from plouf.absolight.net (plouf.absolight.net [212.43.217.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C2F143D1F for ; Sat, 21 Feb 2004 08:01:45 -0800 (PST) (envelope-from mat@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by plouf.absolight.net (Postfix) with ESMTP id F128E60505A; Sat, 21 Feb 2004 17:01:43 +0100 (CET) Received: from cmantatzi.in.t-online.fr (cmantatzi.in.t-online.fr [213.44.126.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id 51DF2605016; Sat, 21 Feb 2004 17:01:43 +0100 (CET) Date: Sat, 21 Feb 2004 17:01:22 +0100 From: Mathieu Arnold To: Nick Twaddell , freebsd-scsi@freebsd.org Message-ID: <2966155.1077382882@cmantatzi.in.t-online.fr> X-Mailer: Mulberry/3.1.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd 0.1 Subject: Re: raid controllers 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: Sat, 21 Feb 2004 16:01:45 -0000 +-le 21/02/04 00:09 -0800, Nick Twaddell =E9crivait : | So who makes a good Raid controller that is fully supported in FreeBSD and = I | can manage it from the command line? Since it doesent look like we will be | seeing an ipssend in freebsd. 3ware does pretty nice ata raid cards, highpoint does too. --=20 Mathieu Arnold From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 21 09:48:57 2004 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 2B00F16A4CE; Sat, 21 Feb 2004 09:48:57 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA77143D1D; Sat, 21 Feb 2004 09:48:56 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i1LHmEDL072353; Sat, 21 Feb 2004 12:48:14 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i1LHmEwN072350; Sat, 21 Feb 2004 12:48:14 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 21 Feb 2004 12:48:14 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Kenneth D. Merry" In-Reply-To: <20040220153213.GA16894@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Colin Percival cc: scsi@freebsd.org Subject: Re: commit approval 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: Sat, 21 Feb 2004 17:48:57 -0000 On Fri, 20 Feb 2004, Kenneth D. Merry wrote: > Looks fine, feel free to commit. Ditto. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 21 21:09:52 2004 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 26FDD16A4CE for ; Sat, 21 Feb 2004 21:09:52 -0800 (PST) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 919A643D1D for ; Sat, 21 Feb 2004 21:09:51 -0800 (PST) (envelope-from dave.edwards@adelaide.on.net) Received: from tfish.chunga.apana.org.au (ppp43-161.lns1.adl1.internode.on.net [150.101.43.161])i1M59nUL037950 for ; Sun, 22 Feb 2004 15:39:50 +1030 (CST) Message-Id: <6.0.1.1.0.20040222153521.0311cb90@mail.internode.on.net> X-Sender: dave.edwards@mail.internode.on.net X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Sun, 22 Feb 2004 15:40:06 +1030 To: freebsd-scsi@freebsd.org From: Dave Edwards Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Compaq ML350G3 with Smart Array 642 with FreeBSD 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: Sun, 22 Feb 2004 05:09:52 -0000 Hi, Anyone using FreeBSD on a Compaq Proliant ML350G3 with Smart Array 642? I'm offered a setup like this for a high IO system (log server) and would just like to make sure that FreeBSD will see the Raid 5 array properly. I can see the ar driver supports quite a long list of Smart Array devices, but I can't see the 642 listed. Does FreeBSD see the hot-swap remove-disk/add-disk events? If so, can the raid array be re-built without shutting down the OS and rebuilding the array from the SCSI card bios? If not, is there a Raid 5 controller that has better support with FreeBSD? Also, do I need to use 5.2 or can I still use the stable branch? Thanks in advance folks. I'll post a summary of replies. ciao dave --- Dave Edwards dave.edwards@adelaide.on.net || davo@chunga.apana.org.au wh: +618 8226 5426 || ah: +618 8365 0024 || Mob: 0408 808 355 Adelaide, South Australia ----