From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 7 11:01:28 2005 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 6DE2B16A509 for ; Mon, 7 Mar 2005 11:01:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3363143D1F for ; Mon, 7 Mar 2005 11:01:28 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j27B1S8U037254 for ; Mon, 7 Mar 2005 11:01:28 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j27B1RMh037248 for freebsd-scsi@freebsd.org; Mon, 7 Mar 2005 11:01:27 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 7 Mar 2005 11:01:27 GMT Message-Id: <200503071101.j27B1RMh037248@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2005 11:01:28 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2000/08/18] kern/20689 scsi Newbusified version of ncr driver does no f [2001/05/03] kern/27059 scsi (symbios) SCSI subsystem hangs under heav o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug f [2002/09/15] kern/42796 scsi NCR/SYM 53C825 driver detects scsi cdrom f [2002/11/25] kern/45713 scsi If you use the amr driver, it is impossib f [2002/12/09] kern/46152 scsi Panic in adw dumping to tape f [2003/05/16] kern/52331 scsi 4.7 to 4.8-REL upgrade: SCSI disks on sym f [2003/09/14] kern/56759 scsi [hang] System freezes when writing CD Adv f [2003/09/14] kern/56760 scsi [hang] system hangs at boot with adaptec f [2003/09/14] kern/56871 scsi dd can't write variable length data block f [2003/09/18] kern/56973 scsi SCSI errors from on-board Adaptec (AIC7xx s [2003/09/30] kern/57398 scsi Current fails to install on mly(4) based o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with a [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/09/15] kern/71778 scsi 5.3 BETA3 doesnt see Adaptec 2015S FW Rev o [2004/12/02] kern/74607 scsi FreeBSD 5.3 install CD crashes on SCSI de o [2004/12/29] kern/75603 scsi 5.3 kernel crash 19 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2001/08/15] kern/29727 scsi [amr] [patch] amr_enquiry3 structure in a o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2003/10/01] kern/57468 scsi [patch] Quirk for Quantum LPS540S o [2003/10/01] kern/57469 scsi [patch] Quirk for Conner CP3500 o [2004/09/22] kern/72010 scsi [patch] mt -f /dev/rsa0.ctl comp off, or 8 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 8 07:06:21 2005 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 3D80716A4CE; Tue, 8 Mar 2005 07:06:21 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C066C43D4C; Tue, 8 Mar 2005 07:06:20 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1D8YnL-000PnZ-9a; Tue, 08 Mar 2005 09:06:19 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: hackers@freebsd.org In-reply-to: Your message of Fri, 25 Feb 2005 12:09:44 +0200 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Mar 2005 09:06:19 +0200 From: Danny Braniss Message-ID: cc: scsi@freebsd.org Subject: Re: iSCSI initiator driver beta version, testers wanted 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, 08 Mar 2005 07:06:21 -0000 well, i guess all is ok, since im not getting much feedback :-) anyways, this is my new problem: o- the target accepts the login, but does not supply a valid device, usually because some admin. problem. I would like to be able to report the problem to the initiator and I need some clues. The cam will, if successful create /dev/da*, on failure nothing, so Q: how can this be found out without getting into the actual SCSI transactions? thanks, danny From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 8 13:47:17 2005 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 CDF2F16A4CE; Tue, 8 Mar 2005 13:47:17 +0000 (GMT) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAFC043D3F; Tue, 8 Mar 2005 13:47:16 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j28Dl4Rj081362; Tue, 8 Mar 2005 07:47:04 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <422DACD4.9030105@centtech.com> Date: Tue, 08 Mar 2005 07:47:00 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: scsi@freebsd.org Subject: Re: iSCSI initiator driver beta version, testers wanted 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, 08 Mar 2005 13:47:18 -0000 Danny Braniss wrote: > well, i guess all is ok, since im not getting much feedback :-) > anyways, this is my new problem: > o- the target accepts the login, but does not supply a valid device, usually > because some admin. problem. I would like to be able to report the problem > to the initiator and I need some clues. The cam will, if successful > create /dev/da*, on failure nothing, so Q: how can this be found out > without getting into the actual SCSI transactions? Is there a target mode implementation of this for FreeBSD yet? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology I have seen the future and it is just like the present, only longer. ------------------------------------------------------------------------ From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 8 14:04:32 2005 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 90C0A16A4CE; Tue, 8 Mar 2005 14:04:32 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A01D43D2D; Tue, 8 Mar 2005 14:04:32 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1D8fK3-000CkV-1n; Tue, 08 Mar 2005 16:04:31 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Eric Anderson In-Reply-To: Message from Eric Anderson of "Tue, 08 Mar 2005 07:47:00 CST." <422DACD4.9030105@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Mar 2005 16:04:30 +0200 From: Danny Braniss Message-ID: cc: hackers@freebsd.org cc: scsi@freebsd.org Subject: Re: iSCSI initiator driver beta version, testers wanted 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, 08 Mar 2005 14:04:32 -0000 > Danny Braniss wrote: > > well, i guess all is ok, since im not getting much feedback :-) > > anyways, this is my new problem: > > o- the target accepts the login, but does not supply a valid device, usually > > because some admin. problem. I would like to be able to report the problem > > to the initiator and I need some clues. The cam will, if successful > > create /dev/da*, on failure nothing, so Q: how can this be found out > > without getting into the actual SCSI transactions? > > > Is there a target mode implementation of this for FreeBSD yet? > speakin for myself, at the moment im trying to get the initiator working, and up to speed, after that i might try and tackle the target, but though there is alot of symmetry, there is much more administrativia involved. danny From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 8 14:07:18 2005 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 31B5816A4CE; Tue, 8 Mar 2005 14:07:18 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8084E43D48; Tue, 8 Mar 2005 14:07:17 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j28E7ARr015966; Tue, 8 Mar 2005 08:07:10 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <422DB18A.6080802@centtech.com> Date: Tue, 08 Mar 2005 08:07:06 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/755/Mon Mar 7 19:00:18 2005 on mh1.centtech.com X-Virus-Status: Clean cc: hackers@freebsd.org cc: scsi@freebsd.org Subject: Re: iSCSI initiator driver beta version, testers wanted 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, 08 Mar 2005 14:07:18 -0000 Danny Braniss wrote: >>Danny Braniss wrote: >> >>>well, i guess all is ok, since im not getting much feedback :-) >>>anyways, this is my new problem: >>>o- the target accepts the login, but does not supply a valid device, usually >>> because some admin. problem. I would like to be able to report the problem >>> to the initiator and I need some clues. The cam will, if successful >>> create /dev/da*, on failure nothing, so Q: how can this be found out >>> without getting into the actual SCSI transactions? >> >> >>Is there a target mode implementation of this for FreeBSD yet? >> > > speakin for myself, > at the moment im trying to get the initiator working, and up to speed, after that > i might try and tackle the target, but though there is alot of symmetry, there is > much more administrativia involved. I'd help you test, but I have no iscsi targets to test against :) Eirc -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology I have seen the future and it is just like the present, only longer. ------------------------------------------------------------------------ From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 8 22:50:28 2005 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 35A6816A4CF; Tue, 8 Mar 2005 22:50:28 +0000 (GMT) Received: from venus.slicmedia.com (dsl-202-173-145-174.qld.westnet.com.au [202.173.145.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD10943D4C; Tue, 8 Mar 2005 22:50:25 +0000 (GMT) (envelope-from simon@quo.com.au) Received: from [192.168.1.150] ([192.168.1.150]) by venus.slicmedia.com (Merak 5.4.2) with ESMTP id KOB36964; Wed, 09 Mar 2005 08:58:42 +1000 Message-ID: <422E2C2D.3060404@quo.com.au> Date: Wed, 09 Mar 2005 08:50:21 +1000 From: Simon Litchfield User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Promise FastTrak Tx4200 & FreeBSD 5.3 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, 08 Mar 2005 22:50:28 -0000 Hi folks Anyone have any ideas on the Promise PDC20319 (Fasttrak S150 TX4)? We intend to run 5.3 release on this machine. Thanks! Simon Litchfield. -- Quo Consulting info@quo.com.au http://www.quo.com.au/ Phone +61 (0)7 5520 2665 Fax +61 (0)2 8569 2377 Level 3 : Old Burleigh Theatre Arcade 66 Goodwin Terrace : Burleigh Heads Queensland : Australia From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 9 11:48:33 2005 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 E804C16A4CE for ; Wed, 9 Mar 2005 11:48:33 +0000 (GMT) Received: from mail.software.plasmon.com (mail.software.plasmon.co.uk [194.130.136.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6668F43D41 for ; Wed, 9 Mar 2005 11:48:33 +0000 (GMT) (envelope-from jconnett@software.plasmon.com) Received: from skylon.devel.pcs ([10.4.2.152]) by mail.software.plasmon.com with esmtp (Exim 3.35 #1 (Debian)) id 1D8zfg-0004Et-00; Wed, 09 Mar 2005 11:48:12 +0000 Message-ID: <422EE22D.8090105@software.plasmon.com> Date: Wed, 09 Mar 2005 11:46:53 +0000 From: John Connett User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1 X-Accept-Language: en MIME-Version: 1.0 To: Scott Long References: <200503031523.j23FN62E022298@corbulon.video-collage.com> <4227F1E3.9030500@samsco.org> In-Reply-To: <4227F1E3.9030500@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Saba Nesar cc: scsi@freebsd.org Subject: Re: need help choosing a SCSI controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 11:48:34 -0000 Scott Long wrote: > LSI is also talking about releasing FreeBSD-native > management apps for their RAID controllers, though it's not clear to > me whether they will support the older models. Any further information available on these management apps? I have an application that runs on a system with an onboard LSI 53C1020A with Integrated Mirroring firmware. This controller can't be used because of the lack of a management app able to query the state of the two disk mirror and command a rebuild. If a suitable managment app was available for either the LSI 53C1020A + IME or LSI 53C1020A + MegaRAID SCSI 320-0 (Zero Channel RAID) this would be a saving on the cost of an Adaptec 2110S which can be managed using raidutil. This is for FreeBSD 4.x. From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 9 15:12:33 2005 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 8D42516A4CE for ; Wed, 9 Mar 2005 15:12:33 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 929D143D4C for ; Wed, 9 Mar 2005 15:12:30 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j29FDQIS080213; Wed, 9 Mar 2005 08:13:26 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <422F11C9.5080402@samsco.org> Date: Wed, 09 Mar 2005 08:10:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Connett References: <200503031523.j23FN62E022298@corbulon.video-collage.com> <4227F1E3.9030500@samsco.org> <422EE22D.8090105@software.plasmon.com> In-Reply-To: <422EE22D.8090105@software.plasmon.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: Saba Nesar cc: scsi@freebsd.org Subject: Re: need help choosing a SCSI controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 15:12:33 -0000 John Connett wrote: > Scott Long wrote: > >> LSI is also talking about releasing FreeBSD-native >> management apps for their RAID controllers, though it's not clear to >> me whether they will support the older models. > > > Any further information available on these management apps? > > I have an application that runs on a system with an onboard LSI 53C1020A > with Integrated Mirroring firmware. This controller can't be used > because of the lack of a management app able to query the state of the > two disk mirror and command a rebuild. > > If a suitable managment app was available for either the LSI 53C1020A + > IME or LSI 53C1020A + MegaRAID SCSI 320-0 (Zero Channel RAID) this would > be a saving on the cost of an Adaptec 2110S which can be managed using > raidutil. > > This is for FreeBSD 4.x. > I don't know of any plans to support management with the MPT-Fusion product line. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 9 15:33:49 2005 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 3990616A4CE for ; Wed, 9 Mar 2005 15:33:49 +0000 (GMT) Received: from gwmail1.grupos.com.br (gwmail1.grupos.com.br [66.90.64.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C03443D3F for ; Wed, 9 Mar 2005 15:33:49 +0000 (GMT) (envelope-from marcus@corp.grupos.com.br) Received: from corp.grupos.com.br (unknown [150.162.166.55]) by gwmail1.grupos.com.br (Postfix) with ESMTP id 47FFE3C0CA for ; Wed, 9 Mar 2005 12:33:48 -0300 (BRT) Received: from [150.162.166.51] (noc.grupos.com.br [150.162.166.51]) by corp.grupos.com.br (Postfix) with ESMTP id 4337B20A1E for ; Wed, 9 Mar 2005 12:33:47 -0300 (BRT) Message-ID: <422F175A.2090809@corp.grupos.com.br> Date: Wed, 09 Mar 2005 12:33:46 -0300 Organization: Grupos Internet S/A From: Marcus Grando User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) 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: Storage Clariion AX100 and Qlogic X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 15:33:49 -0000 Hi List, FreeBSD work's well on Clariion AX100 and HBA Qlogic 22xx? Somebody use in production system? Which best Storage/HBA that work's on FreeBSD? Thanks -- Marcus Grando Grupos Internet S/A marcus(at)corp.grupos.com.br From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 10 00:54:20 2005 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 D721E16A4CE for ; Thu, 10 Mar 2005 00:54:20 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9956C43D1F for ; Thu, 10 Mar 2005 00:54:20 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id j2A0sKL21214 for freebsd-scsi@freebsd.org; Wed, 9 Mar 2005 16:54:20 -0800 (PST) Date: Wed, 9 Mar 2005 16:54:20 -0800 From: Mike Hunter To: freebsd-scsi@freebsd.org Message-ID: <20050310005420.GB20136@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: Dump card states w/ increasing frequency (FBSD 4.8, dual Xeon) 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, 10 Mar 2005 00:54:21 -0000 Hi everybody, About 3 weeks ago, one of my boxes started doing frequent (once or twice a day) dump card states. It's a fbsd machine running 4.8-RELEASE-p16. This was a machine that did a lot of dump card states right when I bought it, which was tracked down to an incompatibility with the builtin adaptec controller, and I switched to an add-on card (29160/N/LP Ultra160 (AIC-7892A) SCSI Host Adapter). I haven't updated the OS recently so it seems unlikely that it's FBSD related, unless increasing load on the box is revealing a previously unseen issue. All the dump card states relate to da2, a 70G seagate disk. Would a disk that's flaking out give these kinds of messages, or is this some kind of controller / OS issue? I'm wondering if I should try replacing the disk or if there any other causes I can investigate. Thanks for any advice, Mike Mar 9 09:55:08 mybox0r /kernel: (da2:ahc0:0:2:0): SCB 0x14 - timed out Mar 9 09:55:23 mybox0r /kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< Mar 9 09:55:23 mybox0r /kernel: ahc0: Dumping Card State while idle, at SEQADDR 0x8 Mar 9 09:55:23 mybox0r /kernel: Card was paused Mar 9 09:55:23 mybox0r /kernel: ACCUM = 0x0, SINDEX = 0x3e, DINDEX = 0xe4, ARG_2 = 0x0 Mar 9 09:55:23 mybox0r /kernel: HCNT = 0x0 SCBPTR = 0x1e Mar 9 09:55:23 mybox0r /kernel: SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] Mar 9 09:55:23 mybox0r /kernel: LASTPHASE[0x1]:(P_BUSFREE) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) Mar 9 09:55:23 mybox0r /kernel: SBLKCTL[0x6]:(SELWIDE|ENAB20) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) Mar 9 09:55:23 mybox0r /kernel: SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x0] Mar 9 09:55:23 mybox0r /kernel: SSTAT1[0x8]:(BUSFREE) SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x8]:(ENSWRAP) Mar 9 09:55:23 mybox0r /kernel: SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) SXFRCTL0[0x80]:(DFON) Mar 9 09:55:23 mybox0r /kernel: DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) Mar 9 09:55:23 mybox0r /kernel: STACK: 0xe9 0x16b 0x111 0x3 Mar 9 09:55:23 mybox0r /kernel: SCB count = 110 Mar 9 09:55:23 mybox0r /kernel: Kernel NEXTQSCB = 16 Mar 9 09:55:23 mybox0r /kernel: Card NEXTQSCB = 16 Mar 9 09:55:23 mybox0r /kernel: QINFIFO entries: Mar 9 09:55:23 mybox0r /kernel: Waiting Queue entries: Mar 9 09:55:23 mybox0r /kernel: Disconnected Queue entries: 25:12 28:90 1:82 4:89 24:57 17:35 18:10 2:13 5:77 3:31 11:39 9:38 8:69 23:78 26:7 13:14 14:20 Mar 9 09:55:23 mybox0r /kernel: QOUTFIFO entries: Mar 9 09:55:23 mybox0r /kernel: Sequencer Free SCB List: 30 12 19 27 22 15 10 21 20 16 31 0 7 6 29 Mar 9 09:55:23 mybox0r /kernel: Sequencer SCB Info: Mar 9 09:55:23 mybox0r /kernel: 0 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 1 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x52] Mar 9 09:55:23 mybox0r /kernel: 2 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xd] Mar 9 09:55:23 mybox0r /kernel: 3 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x1f] Mar 9 09:55:23 mybox0r /kernel: 4 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x59] Mar 9 09:55:23 mybox0r /kernel: 5 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x4d] Mar 9 09:55:23 mybox0r /kernel: 6 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 7 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 8 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x45] Mar 9 09:55:23 mybox0r /kernel: 9 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x26] Mar 9 09:55:23 mybox0r /kernel: 10 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 11 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x27] Mar 9 09:55:23 mybox0r /kernel: 12 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 13 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xe] Mar 9 09:55:23 mybox0r /kernel: 14 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x14] Mar 9 09:55:23 mybox0r /kernel: 15 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 16 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 17 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x23] Mar 9 09:55:23 mybox0r /kernel: 18 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xa] Mar 9 09:55:23 mybox0r /kernel: 19 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 20 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 21 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 22 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 23 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x4e] Mar 9 09:55:23 mybox0r /kernel: 24 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x39] Mar 9 09:55:23 mybox0r /kernel: 25 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xc] Mar 9 09:55:23 mybox0r /kernel: 26 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x7] Mar 9 09:55:23 mybox0r /kernel: 27 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 28 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0x5a] Mar 9 09:55:23 mybox0r /kernel: 29 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x27] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 30 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: 31 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Mar 9 09:55:23 mybox0r /kernel: SCB_LUN[0x0] SCB_TAG[0xff] Mar 9 09:55:23 mybox0r /kernel: Pending list: Mar 9 09:55:23 mybox0r /kernel: 12 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 90 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 82 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 89 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 57 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 35 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 10 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 13 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 77 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 31 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 39 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 38 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 69 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 78 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 7 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 14 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: 20 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x27] SCB_LUN[0x0] Mar 9 09:55:23 mybox0r /kernel: Kernel Free SCB list: 62 36 4 8 43 6 29 19 1 32 15 74 30 83 50 37 47 73 54 88 105 79 42 86 5 99 68 94 28 26 11 80 84 95 18 25 81 55 109 91 58 92 44 85 61 64 21 87 75 66 60 65 52 49 24 9 45 40 53 96 22 23 98 27 104 34 56 17 106 2 59 71 107 67 93 72 63 97 3 108 33 51 70 76 46 41 0 48 103 102 101 100 Mar 9 09:55:23 mybox0r /kernel: Mar 9 09:55:23 mybox0r /kernel: <<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Mar 9 09:55:23 mybox0r /kernel: sg[0] - Addr 0xe421a000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[1] - Addr 0x73dbb000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[2] - Addr 0xb741c000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[3] - Addr 0x28a9d000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[4] - Addr 0x6837e000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[5] - Addr 0x67d1f000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[6] - Addr 0xeda20000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[7] - Addr 0xae41000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[8] - Addr 0xd7f42000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[9] - Addr 0xdb2e3000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[10] - Addr 0xa0ba4000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[11] - Addr 0x74105000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[12] - Addr 0x96e26000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[13] - Addr 0x36b47000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[14] - Addr 0xd348000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: sg[15] - Addr 0x8cd69000 : Length 4096 Mar 9 09:55:23 mybox0r /kernel: (da2:ahc0:0:2:0): Queuing a BDR SCB Mar 9 09:55:23 mybox0r /kernel: (da2:ahc0:0:2:0): Bus Device Reset Message Sent Mar 9 09:55:23 mybox0r /kernel: (da2:ahc0:0:2:0): no longer in timeout, status = 34b Mar 9 09:55:23 mybox0r /kernel: ahc0: Bus Device Reset on A:2. 17 SCBs aborted ----- End forwarded message ----- From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 10 10:50:13 2005 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 001D016A4CE for ; Thu, 10 Mar 2005 10:50:12 +0000 (GMT) Received: from mail.software.plasmon.com (mail.software.plasmon.co.uk [194.130.136.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AE3A43D4C for ; Thu, 10 Mar 2005 10:50:12 +0000 (GMT) (envelope-from jconnett@software.plasmon.com) Received: from skylon.devel.pcs ([10.4.2.152]) by mail.software.plasmon.com with esmtp (Exim 3.35 #1 (Debian)) id 1D9LEw-0004F4-00; Thu, 10 Mar 2005 10:50:02 +0000 Message-ID: <4230260F.9060701@software.plasmon.com> Date: Thu, 10 Mar 2005 10:48:47 +0000 From: John Connett User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1 X-Accept-Language: en MIME-Version: 1.0 To: Scott Long References: <200503031523.j23FN62E022298@corbulon.video-collage.com> <4227F1E3.9030500@samsco.org> <422EE22D.8090105@software.plasmon.com> <422F11C9.5080402@samsco.org> In-Reply-To: <422F11C9.5080402@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Saba Nesar cc: scsi@freebsd.org Subject: Re: need help choosing a SCSI controller 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, 10 Mar 2005 10:50:13 -0000 Scott Long wrote: > John Connett wrote: > >> Scott Long wrote: >> >>> LSI is also talking about releasing FreeBSD-native >>> management apps for their RAID controllers, though it's not clear to >>> me whether they will support the older models. >> >> >> >> Any further information available on these management apps? >> >> I have an application that runs on a system with an onboard LSI 53C1020A >> with Integrated Mirroring firmware. This controller can't be used >> because of the lack of a management app able to query the state of the >> two disk mirror and command a rebuild. >> >> If a suitable managment app was available for either the LSI 53C1020A + >> IME or LSI 53C1020A + MegaRAID SCSI 320-0 (Zero Channel RAID) this would >> be a saving on the cost of an Adaptec 2110S which can be managed using >> raidutil. >> >> This is for FreeBSD 4.x. >> > > I don't know of any plans to support management with the MPT-Fusion > product line. > > Scott > I only have limited familiarity with the LSI Logic product lines but does this imply that these management apps should support the MegaRAID product line, including the SCSI 320-0 (Zero Channel RAID), but not the Integrated Mirroring on the 53C1020A which is from the MPT-Fusion product line? If this is the case, I would be interested in further information on these management apps. From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 10 12:32:43 2005 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 4640616A4CE; Thu, 10 Mar 2005 12:32:43 +0000 (GMT) Received: from cl-mailhost.FernUni-Hagen.de (sycamore.fernuni-hagen.de [132.176.114.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF4A843D66; Thu, 10 Mar 2005 12:32:42 +0000 (GMT) (envelope-from heinricf@mailstore.FernUni-Hagen.de) Received: from mailstore.fernuni-hagen.de ([132.176.114.185]) by cl-mailhost.FernUni-Hagen.de with esmtp (Exim 4.24) id 1D9MqI-0005qc-0U; Thu, 10 Mar 2005 13:32:42 +0100 Received: from [132.176.7.6] (account heinricf [132.176.7.6] verified) by mailstore.fernuni-hagen.de (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 9617274; Thu, 10 Mar 2005 13:32:39 +0100 Message-ID: <42303E74.9060301@fernuni-hagen.de> Date: Thu, 10 Mar 2005 13:32:52 +0100 From: Fritz Heinrichmeyer Organization: Fernuni Hagen User-Agent: Mozilla Thunderbird 1.0 (X11/20050211) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-stable , freebsd-scsi X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-prewhitelist: your reply will pass through without greylisting Subject: error messages from easyraid ex array 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, 10 Mar 2005 12:32:43 -0000 Hello, sometimes i see following messages with FreeBSD-5.3, ahc driver and an easyraid ex system. We have two identical boxes one connected to another system has no problem. The problematic error messages occur when berkeley-db files are massaged by cyrus imap server. I cannot believe there is a media error on an raid 5 system that is not announced at the control panel of the raid box. Driver: ahc2: port 0x3800-0x38ff mem 0xf7ed0000-0xf7ed0fff irq 11 at device 4.0 on pci1 da1 at ahc2 bus 0 target 5 lun 0 Errors: (da1:ahc2:0:5:0): READ(10). CDB: 28 0 0 71 6a 4f 0 0 10 0 (da1:ahc2:0:5:0): CAM Status: SCSI Status Error (da1:ahc2:0:5:0): SCSI Status: Check Condition (da1:ahc2:0:5:0): MEDIUM ERROR asc:0,0 (da1:ahc2:0:5:0): No additional sense information (da1:ahc2:0:5:0): Retrying Command (per Sense Data) -- Mit freundlichen Gruessen Fritz Heinrichmeyer FernUniversitaet, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 10 16:04:32 2005 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 C9D7916A4CE; Thu, 10 Mar 2005 16:04:32 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 239CD43D5A; Thu, 10 Mar 2005 16:04:32 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id j2AG4Twi030489; Thu, 10 Mar 2005 09:04:29 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id j2AG4Tee030488; Thu, 10 Mar 2005 09:04:29 -0700 (MST) (envelope-from ken) Date: Thu, 10 Mar 2005 09:04:29 -0700 From: "Kenneth D. Merry" To: Fritz Heinrichmeyer Message-ID: <20050310160428.GA30406@nargothrond.kdm.org> References: <42303E74.9060301@fernuni-hagen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42303E74.9060301@fernuni-hagen.de> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.83/760/Wed Mar 9 10:12:01 2005 on nargothrond.kdm.org X-Virus-Status: Clean cc: freebsd-scsi cc: freebsd-stable Subject: Re: error messages from easyraid ex array 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, 10 Mar 2005 16:04:32 -0000 On Thu, Mar 10, 2005 at 13:32:52 +0100, Fritz Heinrichmeyer wrote: > Hello, > > sometimes i see following messages with FreeBSD-5.3, ahc driver and an > easyraid ex system. We have two identical boxes one connected to another > system has no problem. The problematic error messages occur when > berkeley-db files are massaged by cyrus imap server. > > I cannot believe there is a media error on an raid 5 system that is not > announced at the control panel of the raid box. Well, firmware on the RAID box will do whatever the authors wrote it to do. In theory, you're right. On a non-critical RAID-5 array, they should be able to recover from any single drive read error. If your array is critical, though (i.e. you've lost one disk), you won't be able to recover from a read error. > Driver: > > ahc2: port 0x3800-0x38ff mem > 0xf7ed0000-0xf7ed0fff irq 11 at device 4.0 on pci1 > da1 at ahc2 bus 0 target 5 lun 0 > > Errors: > > (da1:ahc2:0:5:0): READ(10). CDB: 28 0 0 71 6a 4f 0 0 10 0 > (da1:ahc2:0:5:0): CAM Status: SCSI Status Error > (da1:ahc2:0:5:0): SCSI Status: Check Condition > (da1:ahc2:0:5:0): MEDIUM ERROR asc:0,0 > (da1:ahc2:0:5:0): No additional sense information > (da1:ahc2:0:5:0): Retrying Command (per Sense Data) That's a little bit of a strange error, because they only set the sense key but not the asc/ascq. In any case, it looks like we retried it. If the device was still returning errors, you'd eventually see a "Retries Exhausted" message. Ken -- Kenneth Merry ken@FreeBSD.org From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 11 02:01:34 2005 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 51EF916A4CE for ; Fri, 11 Mar 2005 02:01:34 +0000 (GMT) Received: from pop3.arrk.com (pop3.arrk.com [207.67.234.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06EF143D39 for ; Fri, 11 Mar 2005 02:01:34 +0000 (GMT) (envelope-from jason@arrk.com) Received: from Spooler by pop3.arrk.com (Mercury/32 v4.01b) ID MO00B4F6; 10 Mar 2005 18:00:01 -0800 Received: from spooler by pop3.arrk.com (Mercury/32 v4.01b); 10 Mar 2005 17:59:52 -0800 Received: from admin.arrk.com (207.67.234.2) by pop3.arrk.com (Mercury/32 v4.01b) with ESMTP ID MG00B4F5 (Using SSL/TLS, 3DES, CBC mode, keysize 192 bits) ; 10 Mar 2005 17:59:47 -0800 Message-Id: <6.2.0.14.0.20050310175708.0213f3b8@pop3.arrk.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Thu, 10 Mar 2005 18:00:38 -0800 To: freebsd-scsi@freebsd.org From: Jason Nguyen Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: iSCSI initiator driver beta version, testers wanted 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, 11 Mar 2005 02:01:34 -0000 Hi Danny, I'd be interested in testing out your initiator for FreeBSD. We're running version FreeBSD 5.2.1-RELEASE-p9 and I'd like to try it with our Lefthandnetworks NSM 150s, iSCSI SANS. What would you like me to do, in commenting and reporting bugs? Thanks, Jason Nguyen ARRK Product Development Group IT Manager Tel: 858.626.2391 Fax: 858.410-3702 Email: jason@arrk.com ===================================================== ARRK PDG's Statement regarding confidential information: This email message, and any attached files, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Receipt of this transmission is official notification that any information contained herein as well as any oral discussions referenced herein are to be considered Confidential and Proprietary Information as defined in the ARRK Product Development Group Non-Disclosure/Non-Compete Agreement if one was signed by the recipient or the Business, Company or Organization with whom the recipient is employed. Any aspect of this communication that is considered personal in nature, expression of opinion or not related to the business of ARRK Product Development Group is to be considered the responsibility of the individual sender and not of ARRK Product Development Group which accepts no liability for the personal actions or opinions expressed by its employees. From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 11 22:17:01 2005 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 8802116A4CE for ; Fri, 11 Mar 2005 22:17:01 +0000 (GMT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEE9543D2F for ; Fri, 11 Mar 2005 22:17:00 +0000 (GMT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 5DE083D4B for ; Fri, 11 Mar 2005 17:16:59 -0500 (EST) From: "Dan Langille" To: freebsd-scsi@freebsd.org Date: Fri, 11 Mar 2005 17:16:59 -0500 MIME-Version: 1.0 Message-ID: <4231D28B.28878.564DFBA1@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: how does the scsi chain work? 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, 11 Mar 2005 22:17:01 -0000 Hi folks, I added the following devices to my computer, all in one SCSI chain: sa0: Removable Sequential Access SCSI-2 device sa0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) sa1 at sym0 bus 0 target 6 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) sa2 at sym0 bus 0 target 8 lun 0 sa2: Removable Sequential Access SCSI-2 device sa2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) Then I decided to do some concurrent testing. See below for details. The goal was really to test filling the tape. This exercises both the drive and the tape (all of which are used). Sometimes a single tar takes nearly 4 hours, sometimes it takes only 75 minutes. My question: It doesn't look like the load is shared evenly. Can someone talk a bit about this? That's a pretty general and wide question, I know... [root@lux:/home/dan] # date && time tar cf /dev/nsa2 /usr && time tar cf /dev/nsa2 /usr && time tar cf /dev/nsa2 /usr && ti me tar cf /dev/nsa2 /usr && time tar cf /dev/nsa2 /usr && time tar cf /dev/nsa2 /usr ; date Fri Mar 11 06:21:43 EST 2005 tar: Removing leading '/' from member names real 220m12.162s user 0m50.408s sys 2m44.906s tar: Removing leading '/' from member names real 91m4.119s user 0m41.729s sys 2m18.968s tar: Removing leading '/' from member names real 108m48.709s user 0m40.250s sys 2m18.423s tar: Removing leading '/' from member names tar: usr/home/bacula-restores/stand/help/html.hlp: Write error real 33m27.426s user 0m10.290s sys 0m37.428s Fri Mar 11 13:55:15 EST 2005 [root@lux:/home/dan] # date && time tar cf /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr && time tar c f /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr ; date Thu Mar 10 22:31:57 EST 2005 tar: Removing leading '/' from member names real 75m15.394s user 0m45.666s sys 2m31.039s tar: Removing leading '/' from member names real 114m5.702s user 0m52.549s sys 2m45.939s tar: Removing leading '/' from member names real 156m18.091s user 0m51.538s sys 2m46.858s tar: Removing leading '/' from member names real 119m48.240s user 0m49.670s sys 2m45.721s tar: Removing leading '/' from member names tar: usr/home/bacula-restores/usr/X11R6/share/locale/bs/LC_MESSAGES: Write error real 195m0.408s user 0m38.779s sys 2m13.158s Fri Mar 11 09:32:26 EST 2005 root@lux:/home/dan] # date && time tar cf /dev/nsa1 /usr && time tar cf /dev/nsa1 /usr && time tar cf /dev/nsa1 /usr && time tar cf /dev/n sa1 /usr && time tar cf /dev/nsa1 /usr && time tar cf /dev/nsa1 /usr ; date Thu Mar 10 22:53:40 EST 2005 tar: Removing leading '/' from member names real 103m35.344s user 0m50.394s sys 2m44.732s tar: Removing leading '/' from member names real 112m40.647s user 0m50.555s sys 2m46.049s tar: Removing leading '/' from member names real 152m45.638s user 0m52.656s sys 2m46.040s tar: Removing leading '/' from member names real 201m0.014s user 0m53.838s sys 2m51.051s tar: Removing leading '/' from member names tar: usr/home/bacula- restores/usr/src/contrib/ncurses/form/fld_link.c: Write error real 93m59.622s user 0m22.483s sys 1m8.356s Fri Mar 11 09:57:41 EST 2005 -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 11 23:13:49 2005 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 E1A8D16A4CE for ; Fri, 11 Mar 2005 23:13:48 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72E9243D1D for ; Fri, 11 Mar 2005 23:13:48 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id j2BNDl6Y043451; Fri, 11 Mar 2005 16:13:47 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id j2BNDlsp043450; Fri, 11 Mar 2005 16:13:47 -0700 (MST) (envelope-from ken) Date: Fri, 11 Mar 2005 16:13:47 -0700 From: "Kenneth D. Merry" To: Dan Langille Message-ID: <20050311231347.GA43379@nargothrond.kdm.org> References: <4231D28B.28878.564DFBA1@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4231D28B.28878.564DFBA1@localhost> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.83/761/Thu Mar 10 14:01:48 2005 on nargothrond.kdm.org X-Virus-Status: Clean cc: freebsd-scsi@freebsd.org Subject: Re: how does the scsi chain work? 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, 11 Mar 2005 23:13:49 -0000 On Fri, Mar 11, 2005 at 17:16:59 -0500, Dan Langille wrote: > Hi folks, > > I added the following devices to my computer, all in one SCSI chain: > > sa0: Removable Sequential Access SCSI-2 device > sa0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) > sa1 at sym0 bus 0 target 6 lun 0 > sa1: Removable Sequential Access SCSI-2 device > sa1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) > sa2 at sym0 bus 0 target 8 lun 0 > sa2: Removable Sequential Access SCSI-2 device > sa2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) > > Then I decided to do some concurrent testing. See below for details. > The goal was really to test filling the tape. This exercises both > the drive and the tape (all of which are used). > > Sometimes a single tar takes nearly 4 hours, sometimes it takes only > 75 minutes. > > My question: It doesn't look like the load is shared evenly. Can > someone talk a bit about this? That's a pretty general and wide > question, I know... You might want to look at your media quality. You said that your drives and media are used... In this case you even got a write error. That's pretty indicative of bad media. (Or a drive that needs to be serviced I suppose.) > [root@lux:/home/dan] # date && time tar cf /dev/nsa0 /usr && time > tar cf /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr && time tar c > f /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr && time tar cf > /dev/nsa0 /usr ; date > Thu Mar 10 22:31:57 EST 2005 > tar: Removing leading '/' from member names > > real 75m15.394s > user 0m45.666s > sys 2m31.039s > tar: Removing leading '/' from member names > > real 114m5.702s > user 0m52.549s > sys 2m45.939s > tar: Removing leading '/' from member names > > real 156m18.091s > user 0m51.538s > sys 2m46.858s > tar: Removing leading '/' from member names > > real 119m48.240s > user 0m49.670s > sys 2m45.721s > tar: Removing leading '/' from member names > tar: usr/home/bacula-restores/usr/X11R6/share/locale/bs/LC_MESSAGES: > Write error > > real 195m0.408s > user 0m38.779s > sys 2m13.158s > Fri Mar 11 09:32:26 EST 2005 And you got another write error on this tape: > root@lux:/home/dan] # date && time tar cf /dev/nsa1 /usr && time tar > cf /dev/nsa1 /usr && time tar cf /dev/nsa1 /usr && time tar cf > /dev/n > sa1 /usr && time tar cf /dev/nsa1 /usr && time tar cf /dev/nsa1 > /usr ; date > Thu Mar 10 22:53:40 EST 2005 > tar: Removing leading '/' from member names > > real 103m35.344s > user 0m50.394s > sys 2m44.732s > tar: Removing leading '/' from member names > > real 112m40.647s > user 0m50.555s > sys 2m46.049s > tar: Removing leading '/' from member names > > real 152m45.638s > user 0m52.656s > sys 2m46.040s > tar: Removing leading '/' from member names > > real 201m0.014s > user 0m53.838s > sys 2m51.051s > tar: Removing leading '/' from member names > tar: usr/home/bacula- > restores/usr/src/contrib/ncurses/form/fld_link.c: Write error > > real 93m59.622s > user 0m22.483s > sys 1m8.356s > Fri Mar 11 09:57:41 EST 2005 With a tape, if it can't write in one area, it'll skip down the tape to try to find an area it can write to. So you may just be running into bad areas on the tape. I would recommend buying some new media that is speced to work on those drives, and then try it out. If you still have variable performance and write errors, then you may have a drive problem. Don't forget to run a cleaning tape through if those drives use cleaning tapes. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 11 23:58:59 2005 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 DE38216A4CE for ; Fri, 11 Mar 2005 23:58:59 +0000 (GMT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23C1543D41 for ; Fri, 11 Mar 2005 23:58:59 +0000 (GMT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 66FA83D4B; Fri, 11 Mar 2005 18:58:47 -0500 (EST) From: "Dan Langille" To: "Kenneth D. Merry" Date: Fri, 11 Mar 2005 18:58:47 -0500 MIME-Version: 1.0 Message-ID: <4231EA67.15143.56AB2BB5@localhost> Priority: normal In-reply-to: <20050311231347.GA43379@nargothrond.kdm.org> References: <4231D28B.28878.564DFBA1@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: freebsd-scsi@freebsd.org Subject: Re: how does the scsi chain work? 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, 11 Mar 2005 23:59:00 -0000 On 11 Mar 2005 at 16:13, Kenneth D. Merry wrote: > On Fri, Mar 11, 2005 at 17:16:59 -0500, Dan Langille wrote: > > Hi folks, > > > > I added the following devices to my computer, all in one SCSI chain: > > > > sa0: Removable Sequential Access SCSI-2 device > > sa0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) > > sa1 at sym0 bus 0 target 6 lun 0 > > sa1: Removable Sequential Access SCSI-2 device > > sa1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) > > sa2 at sym0 bus 0 target 8 lun 0 > > sa2: Removable Sequential Access SCSI-2 device > > sa2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) > > > > Then I decided to do some concurrent testing. See below for details. > > The goal was really to test filling the tape. This exercises both > > the drive and the tape (all of which are used). > > > > Sometimes a single tar takes nearly 4 hours, sometimes it takes only > > 75 minutes. > > > > My question: It doesn't look like the load is shared evenly. Can > > someone talk a bit about this? That's a pretty general and wide > > question, I know... > > You might want to look at your media quality. You said that your drives > and media are used... > > In this case you even got a write error. That's pretty indicative of bad > media. (Or a drive that needs to be serviced I suppose.) But that's the tape filling up... surely? That's what the test does... fills the tape. Entirely. Usually, I see bad media with: Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): SPACE. CDB: 11 1 ff ff ff 0 Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): CAM Status: SCSI Status Error Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): SCSI Status: Check Condition Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): MEDIUM ERROR info:ffffffff csi:0,0,f,ba asc:11,0 Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): Unrecovered read error Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): Retries Exhausted Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): unable to backspace over one of double filemarks at end of tape Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): it is possible that this device needs a SA_QUIRK_1FM quirk set for it Feb 15 07:06:53 lux kernel: (sa0:isp0:0:4:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. > > [root@lux:/home/dan] # date && time tar cf /dev/nsa0 /usr && time > > tar cf /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr && time tar c > > f /dev/nsa0 /usr && time tar cf /dev/nsa0 /usr && time tar cf > > /dev/nsa0 /usr ; date > > Thu Mar 10 22:31:57 EST 2005 > > tar: Removing leading '/' from member names > > > > real 75m15.394s > > user 0m45.666s > > sys 2m31.039s > > tar: Removing leading '/' from member names > > > > real 114m5.702s > > user 0m52.549s > > sys 2m45.939s > > tar: Removing leading '/' from member names > > > > real 156m18.091s > > user 0m51.538s > > sys 2m46.858s > > tar: Removing leading '/' from member names > > > > real 119m48.240s > > user 0m49.670s > > sys 2m45.721s > > tar: Removing leading '/' from member names > > tar: usr/home/bacula-restores/usr/X11R6/share/locale/bs/LC_MESSAGES: > > Write error > > > > real 195m0.408s > > user 0m38.779s > > sys 2m13.158s > > Fri Mar 11 09:32:26 EST 2005 > > > And you got another write error on this tape: > > > root@lux:/home/dan] # date && time tar cf /dev/nsa1 /usr && time tar > > cf /dev/nsa1 /usr && time tar cf /dev/nsa1 /usr && time tar cf > > /dev/n > > sa1 /usr && time tar cf /dev/nsa1 /usr && time tar cf /dev/nsa1 > > /usr ; date > > Thu Mar 10 22:53:40 EST 2005 > > tar: Removing leading '/' from member names > > > > real 103m35.344s > > user 0m50.394s > > sys 2m44.732s > > tar: Removing leading '/' from member names > > > > real 112m40.647s > > user 0m50.555s > > sys 2m46.049s > > tar: Removing leading '/' from member names > > > > real 152m45.638s > > user 0m52.656s > > sys 2m46.040s > > tar: Removing leading '/' from member names > > > > real 201m0.014s > > user 0m53.838s > > sys 2m51.051s > > tar: Removing leading '/' from member names > > tar: usr/home/bacula- > > restores/usr/src/contrib/ncurses/form/fld_link.c: Write error > > > > real 93m59.622s > > user 0m22.483s > > sys 1m8.356s > > Fri Mar 11 09:57:41 EST 2005 > > With a tape, if it can't write in one area, it'll skip down the tape to try > to find an area it can write to. So you may just be running into bad areas > on the tape. > > I would recommend buying some new media that is speced to work on those > drives, and then try it out. If you still have variable performance and > write errors, then you may have a drive problem. sa2 was writing to new media. > Don't forget to run a cleaning tape through if those drives use cleaning > tapes. Yep. I got to get me some of that. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/