From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 12 11:02:42 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 545F716A41F for ; Mon, 12 Dec 2005 11:02:42 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96CB643D90 for ; Mon, 12 Dec 2005 11:02:32 +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.4/8.13.4) with ESMTP id jBCB2SlK064760 for ; Mon, 12 Dec 2005 11:02:28 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBCB2QSC064754 for freebsd-scsi@freebsd.org; Mon, 12 Dec 2005 11:02:27 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 12 Dec 2005 11:02:27 GMT Message-Id: <200512121102.jBCB2QSC064754@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 11:02:42 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/03] kern/27059 scsi [sym] SCSI subsystem hangs under heavy lo 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 o [2003/05/24] kern/52638 scsi [panic] SCSI U320 on SMP server won't run s [2003/09/30] kern/57398 scsi [mly] Current fails to install on mly(4) o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with o [2003/12/27] kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C81 s [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/12/02] kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5 o [2005/06/04] kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceP 11 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/57469 scsi [scsi] [patch] Quirk for Conner CP3500 o [2005/01/12] kern/76178 scsi [ahd] Problem with ahd and large SCSI Rai 7 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 13 17:00:45 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 B843E16A41F for ; Tue, 13 Dec 2005 17:00:45 +0000 (GMT) (envelope-from rand@meridian-enviro.com) Received: from newman.meridian-enviro.com (newman.meridian-enviro.com [207.109.235.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9005E43D45 for ; Tue, 13 Dec 2005 17:00:44 +0000 (GMT) (envelope-from rand@meridian-enviro.com) X-Envelope-To: freebsd-scsi@freebsd.org Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by newman.meridian-enviro.com (8.13.1/8.13.1) with ESMTP id jBDH0g3X055859; Tue, 13 Dec 2005 11:00:43 -0600 (CST) (envelope-from rand@meridian-enviro.com) Received: (from rand@localhost) by delta.meridian-enviro.com (8.13.3/8.13.3/Submit) id jBDH0g0r007037; Tue, 13 Dec 2005 11:00:42 -0600 (CST) (envelope-from rand@delta.meridian-enviro.com) To: "Marc G. Fournier" References: <20051207194635.V1480@ganymede.hub.org> From: rand@meridian-enviro.com (Douglas K. Rand) Date: 13 Dec 2005 11:00:42 -0600 In-Reply-To: <20051207194635.V1480@ganymede.hub.org> Message-ID: <878xup3pad.fsf@delta.meridian-enviro.com> Lines: 26 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: ClamAV 0.84/1209/Mon Dec 12 09:48:01 2005 on newman.meridian-enviro.com X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: ICP driver with FreeBSD 4.x ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:00:45 -0000 ** On Wed, 7 Dec 2005 19:57:12 -0400 (AST), "Marc G. Fournier" said: Marc> I've been trying to get icpcon available at Marc> http://www.vortex.de/english/download/rz_neu/freebsd/frbsd_e.htm Marc> to work on my 4.x-STABLE server ... after talking to the techs, Marc> I've been told that I have to install the driver available on Marc> that web page, since the one in 4.x is outdated ... Yup, the only way we've gotten icpcon to work on 4.x systems is to replace the FreeBSD iir with the one from ICP. Marc> Can someone comment on the safety of upgrading that driver to Marc> the one that they have on their web site on a live server? Are Marc> there any ramifications, or risks, with doing this? We have had no problems at all using ICP's driver on 4.x systems. Our procedure is to put the iir device into the kernel and replace the contents of the /usr/src/sys/dev/iir directory with ICP's. We have not tried the kernel module. We have ICP cards (the 4 port SATA GDT8546RZ card) in both 4.11 and 4.10 systems. (We also have them on 5.4 and 6.0 systems with the stock FreeBSD iir driver, and an updated icpcon package from ICP works fine with those.) From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 14 19:07:21 2005 Return-Path: X-Original-To: freebsd-scsi@hub.freebsd.org Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFF5816A438; Wed, 14 Dec 2005 19:07:21 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E0D943D5E; Wed, 14 Dec 2005 19:07:21 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBEJ7Dsb085098; Wed, 14 Dec 2005 19:07:13 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBEJ7DlF085094; Wed, 14 Dec 2005 19:07:13 GMT (envelope-from linimon) Date: Wed, 14 Dec 2005 19:07:13 GMT From: Mark Linimon Message-Id: <200512141907.jBEJ7DlF085094@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-scsi@FreeBSD.org Cc: Subject: Re: kern/90282: [sym] SCSI bus resets cause loss of ch device X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 19:07:22 -0000 Synopsis: [sym] SCSI bus resets cause loss of ch device Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: linimon Responsible-Changed-When: Wed Dec 14 19:07:06 UTC 2005 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=90282 From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 15 10:22:36 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 1106116A41F for ; Thu, 15 Dec 2005 10:22:36 +0000 (GMT) (envelope-from kern@sibbald.com) Received: from matou.sibbald.com (matou.sibbald.com [194.158.240.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4966A43D4C for ; Thu, 15 Dec 2005 10:22:34 +0000 (GMT) (envelope-from kern@sibbald.com) Received: from rufus (rufus [192.168.68.112]) by matou.sibbald.com (8.13.4/8.13.4) with ESMTP id jBFAMXKZ003015 for ; Thu, 15 Dec 2005 11:22:33 +0100 Content-Disposition: inline From: Kern Sibbald To: freebsd-scsi@freebsd.org Date: Thu, 15 Dec 2005 11:22:34 +0100 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200512151122.34949.kern@sibbald.com> Subject: Tape drive handling on FreeBSD X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 10:22:36 -0000 Hello, We correponded a couple of years ago when Bacula was experiencing data loss at the end of tapes -- it turned out to be a pthreads bug that suppressed the early end of tape warning. I have a new problem, and if you cannot help, please direct me in the right direction. Basically Bacula (network backup program) needs to open() the tape drive so that it can read/write it. On both Linux and Solaris, it is possible to open the drive with O_NONBLOCK and get a descriptor that can be used for ioctl() calls and providing there is a tape in the drive, it can be used for read() and write(). On FreeBSD, if there is no tape in the drive, the OS always immediately returns errno=ENXIO "Device not configured". This means that on FreeBSD, if there is no tape in the drive, that drive is totally unusable by Bacula. Now it seems to me that there are two solutions: 1. Modify Bacula and system dependent code that opens the control device to see if a tape drive is really there or not, and then rewrite the tape driver code to deal with the fact that if you cannot open a device, it may really be there, and you should continue trying to open it between asking the user to mount it. This is clearly possible. 2. Consider implementing something in FreeBSD as exists on at least Linux and Solaris -- i.e. a means to open the drive and get a valid file descriptor. If you read/write/rewind/... a drive opened and there is no tape, it should either return EIO or better ENOMEDIUM. Comments? -- Best regards, Kern ("> /\ V_V ------------------------------------------------------- -- Best regards, Kern ("> /\ V_V From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 15 15:31:11 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 1C7C216A41F for ; Thu, 15 Dec 2005 15:31:11 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0A5D43D5D for ; Thu, 15 Dec 2005 15:31:08 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.152] (cpe-69-207-238-239.maine.res.rr.com [69.207.238.239]) by ms-smtp-02.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id jBFFV3DL003039 for ; Thu, 15 Dec 2005 10:31:06 -0500 (EST) Date: Thu, 15 Dec 2005 10:31:00 -0800 (PST) From: bmiele@ipnstock.com To: freebsd-scsi@freebsd.org Message-ID: <20051215101820.S1010@payswan.miggles.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Help with HP MSA 1500cs and DL380 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 15:31:11 -0000 Hello, Recently, my company moved my storage from 4 HP MSA30 scsi shelves (2 per machine mirrored) to two HP MSA 1500cs SAN devices. I have moved the MSA30 shelves into the SAN, and also have 4 (2 per msa1500cs) MSA20 SATA shelves. I am running into more then a few issues getting these units, particularily the MSA20s, happy. HP is giving me a hard time because freebsd is not a supported OS, and i am sort of lost and looking for resources specific to this combination. my setups are two identical dl380 machines running 5.4-Stable from Aug. 4. I am using the HP OEM Qlogic 2313 fiber card which uses the isp driver. each machine is attached to a msa1500cs with 4 shelves, 2 msa20 and two msa30. The msa1500c and all shelves are running the most recent firmware. I have each SAN broken into 5 luns, the two msa20 scsi shelves are dedicated entirely to 1.5T volumes, and the two msa30 shelves have been broken into 3 1.4T volumes. They are raid 5, with a 64kB. Both units have given me bus reset errors and timeout errors. Yesterday, one of the msa20 shelves just freaked out and went away. really, any tips at all about where to find resources for a setup like this would be gratefully appreciated. I can provide any information that I have neglected as well. thanks, Brad ------------------------------------------------------------ Brad Miele IPNStock bmiele@ipnstock.com From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 15 18:43:46 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 1FD7716A41F for ; Thu, 15 Dec 2005 18:43:46 +0000 (GMT) (envelope-from acex5@syncer.de) Received: from titanium.webpack.hosteurope.de (titanium.webpack.hosteurope.de [217.115.142.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DCB43D62 for ; Thu, 15 Dec 2005 18:43:45 +0000 (GMT) (envelope-from acex5@syncer.de) Received: by titanium.webpack.hosteurope.de running Exim 4.51 using esmtpa from dslb-084-059-219-194.pools.arcor-ip.net ([84.59.219.194] helo=[192.168.0.100]) id 1Emy4t-00050q-3x; Thu, 15 Dec 2005 19:43:43 +0100 Message-ID: <43A1B967.2010601@syncer.de> Date: Thu, 15 Dec 2005 19:43:51 +0100 From: Sebastian Koehler User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org, bmiele@ipnstock.com X-Enigmail-Version: 0.93.0.0 OpenPGP: id=DFB7BC45 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Subject: Help with HP MSA 1500cs and DL380 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 18:43:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Brad, it seems that you use a direct attached SAN environment. There are no switches are involved, right? Is this a single or multipath setup? The QLA2312 should have 2 FC-ports. What is the HP name for this HBA? FC2214(DC)? Please post some errors and lun assignment. You spoke about firmware versions. To prevent possible SCSI bus resets/timeouts you need to use version 4.98 on MSA1500cs and 1.38 or 1.40 on MSA20. Use ACU-XE to set your FreeBSD hosts to Solaris or other. Did you have the lastest firmware on the HBA, too? Best regards, Sebastian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDoblnufwF6d+3vEURAhKnAJ4kjrVhtLJ8lJiWUpdrEqVy33VPagCgwUrP U0HRXRh00Mr5mVSjBM8nmZk= =qp3E -----END PGP SIGNATURE----- From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 15 20:01:11 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 E6D1E16A420 for ; Thu, 15 Dec 2005 20:01:11 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B4D743D5A for ; Thu, 15 Dec 2005 20:01:11 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.152] (cpe-69-207-238-239.maine.res.rr.com [69.207.238.239]) by ms-smtp-02.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id jBFK14DL012155; Thu, 15 Dec 2005 15:01:06 -0500 (EST) Date: Thu, 15 Dec 2005 15:00:59 -0800 (PST) From: Brad Miele To: Sebastian Koehler In-Reply-To: <43A1B967.2010601@syncer.de> Message-ID: <20051215140240.X1010@payswan.miggles.org> References: <43A1B967.2010601@syncer.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-scsi@freebsd.org Subject: Re: Help with HP MSA 1500cs and DL380 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 20:01:12 -0000 Sebastian, Thanks for the quick reply! On Thu, 15 Dec 2005, Sebastian Koehler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Brad, > > it seems that you use a direct attached SAN environment. There are no > switches are involved, right? correct > Is this a single or multipath setup? single > The > QLA2312 should have 2 FC-ports. What is the HP name for this HBA? > FC2214(DC)? the card has a single fc port, its HP name is: FCA2214 http://h18006.www1.hp.com/products/quickspecs/11711_na/11711_na.html > Please post some errors and lun assignment. the most common error that i see is this: Dec 14 13:48:15 bwayipn04 kernel: isp0: command timed out for 0.125.4 I get about 5 of these a day. the system seems to recover, but the attached FreeBSD server locks up briefly while it is working it out it seems. the other, rarer errors are: Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): READ(06). CDB: 8 0 1 1f 20 0 Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): CAM Status: SCSI Status Error Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): SCSI Status: Check Condition Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): UNIT ATTENTION asc:29,0 Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): Power on, reset, or bus device reset occurred Dec 15 03:01:00 bwayipn04 kernel: (da5:isp0:0:125:6): Retrying Command (per Sense Data) interestingly enough, da5 has no data on it yet, and the device was relatively inactive at 3am EST. here is the output from show units on one of the msa1500cs: Unit 1: In PDLA mode, Unit 1 is Lun 2; In VSA mode, Unit 1 is Lun 1. Unit Identifier : nfsdata02 Device Identifier : 600508B3-00918B90-F30CB219-4D120000 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 13 Data Disk(s) used by lun 1: Disk101: Box 1, Bay 01, (B:T:L 0:00:00) Disk102: Box 1, Bay 02, (B:T:L 0:01:00) Disk103: Box 1, Bay 03, (B:T:L 0:02:00) Disk104: Box 1, Bay 04, (B:T:L 0:03:00) Disk105: Box 1, Bay 05, (B:T:L 0:04:00) Disk106: Box 1, Bay 06, (B:T:L 0:05:00) Disk107: Box 1, Bay 07, (B:T:L 0:08:00) Disk108: Box 1, Bay 08, (B:T:L 0:09:00) Disk109: Box 1, Bay 09, (B:T:L 0:10:00) Disk110: Box 1, Bay 10, (B:T:L 0:11:00) Disk111: Box 1, Bay 11, (B:T:L 0:12:00) Disk112: Box 1, Bay 12, (B:T:L 0:13:00) Disk113: Box 1, Bay 13, (B:T:L 0:14:00) Spare Disk(s) used by lun 1: Disk114: Box 1, Bay 14, (B:T:L 0:15:00) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,680,165MB Unit 2: In PDLA mode, Unit 2 is Lun 3; In VSA mode, Unit 2 is Lun 2. Unit Identifier : nfsdata03 Device Identifier : 600508B3-00918B90-80170E3B-73B20001 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 13 Data Disk(s) used by lun 2: Disk201: Box 2, Bay 01, (B:T:L 1:00:00) Disk202: Box 2, Bay 02, (B:T:L 1:01:00) Disk203: Box 2, Bay 03, (B:T:L 1:02:00) Disk204: Box 2, Bay 04, (B:T:L 1:03:00) Disk205: Box 2, Bay 05, (B:T:L 1:04:00) Disk206: Box 2, Bay 06, (B:T:L 1:05:00) Disk207: Box 2, Bay 07, (B:T:L 1:08:00) Disk208: Box 2, Bay 08, (B:T:L 1:09:00) Disk209: Box 2, Bay 09, (B:T:L 1:10:00) Disk210: Box 2, Bay 10, (B:T:L 1:11:00) Disk211: Box 2, Bay 11, (B:T:L 1:12:00) Disk212: Box 2, Bay 12, (B:T:L 1:13:00) Disk213: Box 2, Bay 13, (B:T:L 1:14:00) Spare Disk(s) used by lun 2: Disk214: Box 2, Bay 14, (B:T:L 1:15:00) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,680,165MB Unit 3: In PDLA mode, Unit 3 is Lun 4; In VSA mode, Unit 3 is Lun 3. Unit Identifier : Device Identifier : 600508B3-00918B90-FD923254-252D0005 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 7 Data Disk(s) used by lun 3: Disk301: Box 3, Bay 01, (B:T:L 2:03:01) Disk302: Box 3, Bay 02, (B:T:L 2:03:02) Disk303: Box 3, Bay 03, (B:T:L 2:03:03) Disk304: Box 3, Bay 04, (B:T:L 2:03:04) Disk305: Box 3, Bay 05, (B:T:L 2:03:05) Disk306: Box 3, Bay 06, (B:T:L 2:03:06) Disk307: Box 3, Bay 07, (B:T:L 2:03:07) Spare Disk(s) used by lun 3: Disk308: Box 3, Bay 08, (B:T:L 2:03:08) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,430,640MB Unit 4: In PDLA mode, Unit 4 is Lun 5; In VSA mode, Unit 4 is Lun 4. Unit Identifier : Device Identifier : 600508B3-00918B90-8DE42743-35F40006 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 7 Data Disk(s) used by lun 4: Disk309: Box 3, Bay 09, (B:T:L 2:03:09) Disk310: Box 3, Bay 10, (B:T:L 2:03:10) Disk311: Box 3, Bay 11, (B:T:L 2:03:11) Disk312: Box 3, Bay 12, (B:T:L 2:03:12) Disk701: Box 7, Bay 01, (B:T:L 2:04:01) Disk702: Box 7, Bay 02, (B:T:L 2:04:02) Disk703: Box 7, Bay 03, (B:T:L 2:04:03) Spare Disk(s) used by lun 4: Disk704: Box 7, Bay 04, (B:T:L 2:04:04) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,430,640MB Unit 5: In PDLA mode, Unit 5 is Lun 6; In VSA mode, Unit 5 is Lun 5. Unit Identifier : Device Identifier : 600508B3-00918B90-3C177166-9E2D0007 Cache Status : Enabled Max Boot Partition: Enabled Volume Status : VOLUME OK Parity Init Status: Complete 7 Data Disk(s) used by lun 5: Disk705: Box 7, Bay 05, (B:T:L 2:04:05) Disk706: Box 7, Bay 06, (B:T:L 2:04:06) Disk707: Box 7, Bay 07, (B:T:L 2:04:07) Disk708: Box 7, Bay 08, (B:T:L 2:04:08) Disk709: Box 7, Bay 09, (B:T:L 2:04:09) Disk710: Box 7, Bay 10, (B:T:L 2:04:10) Disk711: Box 7, Bay 11, (B:T:L 2:04:11) Spare Disk(s) used by lun 5: Disk712: Box 7, Bay 12, (B:T:L 2:04:12) Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5) stripe_size=64kB Logical Volume Capacity : 1,430,640MB > You spoke about firmware versions. To prevent possible SCSI bus > resets/timeouts you need to use version 4.98 on MSA1500cs and 1.38 or > 1.40 on MSA20. here is the version output from one of the msa1500cs MSA1500 Firmware Revision: 4.98b401 (SGA0534040) MSA1500 Hardware Revision: 7 [AutoRev: 0x010000] Fibre Module AutoRev: 0x020000 SCSI I/O Module Bus 0 Revision: 2.02 SCSI I/O Module Bus 1 Revision: 2.02 SCSI I/O Module Bus 2 Revision: 2.02 SCSI I/O Module Bus 3 Revision: <> Fan Control Module A Revision: 2.36 Fan Control Module B Revision: 2.36 Box 1 PROLIANT 4LEE Rev: CP20 (Z8FNLMPX47) Box 2 PROLIANT 4LEE Rev: CP20 (Z8DYLMPX47) Box 3 PROLIANT 8LCE Rev: 1.40 (E05TMLJ15L) Box 3 Fan Control Module A Rev: 2.36 Box 3 Fan Control Module B Rev: 2.36 Box 7 PROLIANT 8LCE Rev: 1.40 (E048MLJ15L) Box 7 Fan Control Module A Rev: 2.36 Box 7 Fan Control Module B Rev: 2.36 > Use ACU-XE to set your FreeBSD hosts to Solaris or other. is ACU-XE something that i can run with FreeBSD attached hosts? I have been limited to using CLI connected via serial so far. what does the host setting do? the docs seem vague on its role. and between solaris and other, is there a preference? > Did you have the lastest firmware on the HBA, too? yes > > Best regards, > Sebastian thanks again! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (Darwin) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFDoblnufwF6d+3vEURAhKnAJ4kjrVhtLJ8lJiWUpdrEqVy33VPagCgwUrP > U0HRXRh00Mr5mVSjBM8nmZk= > =qp3E > -----END PGP SIGNATURE----- > Brad ------------------------------------------------------------ Brad Miele IPNStock bmiele@ipnstock.com From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 16 09:52:48 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 A9D2A16A41F for ; Fri, 16 Dec 2005 09:52:48 +0000 (GMT) (envelope-from acex5@syncer.de) Received: from titanium.webpack.hosteurope.de (titanium.webpack.hosteurope.de [217.115.142.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0AD743D5C for ; Fri, 16 Dec 2005 09:52:37 +0000 (GMT) (envelope-from acex5@syncer.de) Received: by titanium.webpack.hosteurope.de running Exim 4.51 using esmtpa from dslb-084-059-219-130.pools.arcor-ip.net ([84.59.219.130] helo=[192.168.0.100]) id 1EnCFx-00011Z-GG; Fri, 16 Dec 2005 10:52:05 +0100 Message-ID: <43A28E4E.9010501@syncer.de> Date: Fri, 16 Dec 2005 10:52:14 +0100 From: Sebastian Koehler User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brad Miele , freebsd-scsi@freebsd.org References: <43A1B967.2010601@syncer.de> <20051215140240.X1010@payswan.miggles.org> In-Reply-To: <20051215140240.X1010@payswan.miggles.org> X-Enigmail-Version: 0.93.0.0 OpenPGP: id=DFB7BC45 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Help with HP MSA 1500cs and DL380 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 09:52:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Brad, FCA2214 should run firmware 1.45 for hosts other than Windows. Did you notice ispfw(4) and isp(4)? They are talking about a different kind of firmware for the HBA. Maybe you should rebuild your kernel with device isp # For one or more SCSI busses: device scbus0 device ispfw to use the FreeBSD provided firmware. Please connect via serial line to the MSA1000 controller. Enter the command show TECH_SUPPORT. You can also connect the MSA1000 serial cable to the MSA20 serial port and activate the debugging output by pressing the TAB key. This would be only helpfull, if we know that on of the MSA20 boxes got a problem. MSA 1000/1500 cs Command Line Interface http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00149849/c00149849.pdf Page 50 show how to configure a connection profile. You need to set it to "Solaris". CLI> ADD CONNECTION ABC WWPN=12345678-12345678 PROFILE=SOLARIS Why do you use 3 I/O Modules in the MSA1500cs? Which MSAx0 is attached to which I/O module and to which port? Please check that each MSA30 is connected to the SCSI port on the I/O module and MSA20 to a SATA capable port. By the way, its not recommended to spread arrays across different boxes. If one box fail, more than an array will be down. ACU-XE or ACU is a web-based application which can be used to configure the array. You can only launch it by booting up the MSA1500cs support CD, cause it is not available on FreeBSD. MSA1500 Support Software CD http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=415598&swItem=co-22975-3&prodNameId=415600&swEnvOID=1097&swLang=13&mode=4&idx=0 Which version of FreeBSD you are running? (uname -a) Regards, Sebastian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDoo5NufwF6d+3vEURAlqQAKCV3/vv1ANmkUYI3eaBakZaC/zZAgCfTfqw 4P2JFX4FGfH/H5aUAUMOVsA= =TrE2 -----END PGP SIGNATURE----- From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 16 13:58:35 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 B902D16A41F for ; Fri, 16 Dec 2005 13:58:35 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-01.nyroc.rr.com (ms-smtp-01.nyroc.rr.com [24.24.2.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D20043D5D for ; Fri, 16 Dec 2005 13:58:33 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.152] (cpe-69-207-238-239.maine.res.rr.com [69.207.238.239]) by ms-smtp-01.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id jBGDwTFf026393; Fri, 16 Dec 2005 08:58:30 -0500 (EST) Date: Fri, 16 Dec 2005 08:58:24 -0800 (PST) From: Brad Miele To: Sebastian Koehler In-Reply-To: <43A28E4E.9010501@syncer.de> Message-ID: <20051216084651.E71298@payswan.miggles.org> References: <43A1B967.2010601@syncer.de> <20051215140240.X1010@payswan.miggles.org> <43A28E4E.9010501@syncer.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-scsi@freebsd.org Subject: Re: Help with HP MSA 1500cs and DL380 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 13:58:35 -0000 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Brad, > > FCA2214 should run firmware 1.45 for hosts other than Windows. Did you > notice ispfw(4) and isp(4)? They are talking about a different kind of > firmware for the HBA. Maybe you should rebuild your kernel with > > device isp > # For one or more SCSI busses: > device scbus0 > device ispfw > > to use the FreeBSD provided firmware. ahhhh, i think that i am doing this, I am loading ispfw via /boot/loader.conf .do you think statically compiling it is a better method? > > Please connect via serial line to the MSA1000 controller. Enter the > command show TECH_SUPPORT. You can also connect the MSA1000 serial cable > to the MSA20 serial port and activate the debugging output by pressing > the TAB key. This would be only helpfull, if we know that on of the > MSA20 boxes got a problem. > > MSA 1000/1500 cs Command Line Interface > http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00149849/c00149849.pdf > > Page 50 show how to configure a connection profile. You need to set it > to "Solaris". > CLI> ADD CONNECTION ABC WWPN=12345678-12345678 PROFILE=SOLARIS excellent, i have done this on both boxes > > Why do you use 3 I/O Modules in the MSA1500cs? Which MSAx0 is attached > to which I/O module and to which port? Please check that each MSA30 is > connected to the SCSI port on the I/O module and MSA20 to a SATA capable > port. this is because HP says that you cannot have a SCSI shelf and a SATA shelf sharing an I/O module, and each Module can only support one scsi connection. so i have the 2 SATA shelves sharing an I/O Module, and the SCSI shelves each have their own. the SCSI shelves are on the first two I/O modules, and the SATA shelves are on the third. > By the way, its not recommended to spread arrays across different boxes. > If one box fail, more than an array will be down. thanks, i will adjust this today, I was concerned that there would be an issue with having UFS volumes > 2T. Is this not an issue with UFS2? > Which version of FreeBSD you are running? (uname -a) FreeBSD bwayipn04.ipnstock.com 5.4-STABLE FreeBSD 5.4-STABLE #1: Thu Aug 4 17:31:22 EDT 2005 root@bwayipn04.ipnstock.com:/usr/obj/usr/src/sys/BWAYIPN0420050803 i386 I am thinking that I will be upping to 6-Stable at some point when i am on location in January (the machines are in new york, and i am in Maine). I am sort of watching the lists for any dl380 shakeout isues with 6 before i make the leap. thanks again Sebastian > > Regards, > Sebastian > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (Darwin) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFDoo5NufwF6d+3vEURAlqQAKCV3/vv1ANmkUYI3eaBakZaC/zZAgCfTfqw > 4P2JFX4FGfH/H5aUAUMOVsA= > =TrE2 > -----END PGP SIGNATURE----- > Brad ------------------------------------------------------------ Brad Miele VP Technology IPNStock (866)476-7862 x902 bmiele@ipnstock.com On Fri, 16 Dec 2005, Sebastian Koehler wrote: From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 16 16:26:26 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 3913E16A434 for ; Fri, 16 Dec 2005 16:26:26 +0000 (GMT) (envelope-from acex5@syncer.de) Received: from titanium.webpack.hosteurope.de (titanium.webpack.hosteurope.de [217.115.142.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88FFD43D9B for ; Fri, 16 Dec 2005 16:25:20 +0000 (GMT) (envelope-from acex5@syncer.de) Received: by titanium.webpack.hosteurope.de running Exim 4.51 using esmtpa from dslb-084-059-219-130.pools.arcor-ip.net ([84.59.219.130] helo=[192.168.0.100]) id 1EnIOR-0001Co-Lp; Fri, 16 Dec 2005 17:25:15 +0100 Message-ID: <43A2EA6B.6070407@syncer.de> Date: Fri, 16 Dec 2005 17:25:15 +0100 From: Sebastian Koehler User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brad Miele , freebsd-scsi@freebsd.org References: <43A1B967.2010601@syncer.de> <20051215140240.X1010@payswan.miggles.org> <43A28E4E.9010501@syncer.de> <20051216084651.E71298@payswan.miggles.org> In-Reply-To: <20051216084651.E71298@payswan.miggles.org> X-Enigmail-Version: 0.93.0.0 OpenPGP: id=DFB7BC45 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Help with HP MSA 1500cs and DL380 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 16:26:27 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brad, regarding man page there should be no difference between static and dynamic load of ispfw. What type of connection profile was used before changing? I've checked the setup guide and your right, mixing SCSI and SATA on the same I/O module is not supported. This feature was announced some time ago, but is still not available. The MSA1000 controller used only support 2TB LUNs. Please consider this. UFS2 itself support much larger logical drives (64 bit addressing). Have a nice weekend, Sebastian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDoupqufwF6d+3vEURAquHAJ4ogUyiOL6zSaAth+1IWKjIXhxsQgCfXpKL 0j3fKad1rPED2mbfuepOKvQ= =eJei -----END PGP SIGNATURE----- From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 16 16:57:36 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 7221A16A420 for ; Fri, 16 Dec 2005 16:57:36 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-04.nyroc.rr.com (ms-smtp-04.nyroc.rr.com [24.24.2.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56D4443D67 for ; Fri, 16 Dec 2005 16:57:28 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.152] (cpe-69-207-238-239.maine.res.rr.com [69.207.238.239]) by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id jBGGvORE022419; Fri, 16 Dec 2005 11:57:24 -0500 (EST) Date: Fri, 16 Dec 2005 11:57:18 -0800 (PST) From: Brad Miele To: Sebastian Koehler In-Reply-To: <43A2EA6B.6070407@syncer.de> Message-ID: <20051216115506.L71298@payswan.miggles.org> References: <43A1B967.2010601@syncer.de> <20051215140240.X1010@payswan.miggles.org> <43A28E4E.9010501@syncer.de> <20051216084651.E71298@payswan.miggles.org> <43A2EA6B.6070407@syncer.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-scsi@freebsd.org Subject: Re: Help with HP MSA 1500cs and DL380 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 16:57:36 -0000 sebastian, I am going to wath it with the changes that i have made, so far the biggest was changing the profile from the default, which the docs say is windows, to solaris. you cannot create a lun larger then 2T, i found that out when i tried earlier. i will see if changing the profile has any effect on the timeout issues that I am seeing. it does seem that some of the options in solaris are different from those in the default. have a good weekend. Brad ------------------------------------------------------------ Brad Miele VP Technology IPNStock (866)476-7862 x902 bmiele@ipnstock.com On Fri, 16 Dec 2005, Sebastian Koehler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Brad, > > regarding man page there should be no difference between static and > dynamic load of ispfw. What type of connection profile was used before > changing? I've checked the setup guide and your right, mixing SCSI and > SATA on the same I/O module is not supported. This feature was announced > some time ago, but is still not available. The MSA1000 controller used > only support 2TB LUNs. Please consider this. UFS2 itself support much > larger logical drives (64 bit addressing). > > Have a nice weekend, > Sebastian > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (Darwin) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFDoupqufwF6d+3vEURAquHAJ4ogUyiOL6zSaAth+1IWKjIXhxsQgCfXpKL > 0j3fKad1rPED2mbfuepOKvQ= > =eJei > -----END PGP SIGNATURE----- > From owner-freebsd-scsi@FreeBSD.ORG Sun Dec 18 00:00:06 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 E701016A41F for ; Sun, 18 Dec 2005 00:00:06 +0000 (GMT) (envelope-from dan@langille.org) Received: from m21.unixathome.org (m21.unixathome.org [205.150.199.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3280043D49 for ; Sun, 18 Dec 2005 00:00:06 +0000 (GMT) (envelope-from dan@langille.org) Received: from localhost (localhost [205.150.199.217]) by m21.unixathome.org (Postfix) with ESMTP id 58E4CBFB5 for ; Sat, 17 Dec 2005 19:00:03 -0500 (EST) Received: from m21.unixathome.org ([205.150.199.217]) by localhost (m21.unixathome.org [205.150.199.217]) (amavisd-new, port 10024) with ESMTP id 05976-09 for ; Sat, 17 Dec 2005 19:00:00 -0500 (EST) Received: from bast.unixathome.org (bast.unixathome.org [70.26.229.230]) by m21.unixathome.org (Postfix) with ESMTP id 32301BFB1 for ; Sat, 17 Dec 2005 19:00:00 -0500 (EST) Received: from wocker (wocker.unixathome.org [10.55.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 1443E3D3B for ; Sat, 17 Dec 2005 19:00:00 -0500 (EST) From: "Dan Langille" To: freebsd-scsi@freebsd.org Date: Sat, 17 Dec 2005 19:00:00 -0500 MIME-Version: 1.0 Message-ID: <43A46030.31260.5B3110E@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 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at unixathome.org Subject: no tape - ENXIO - device not configured X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2005 00:00:07 -0000 You probably know that I'm a developer on the Bacula project. One of the issues we're trying to improve now is using the tape drive when there is no tape. Basically Bacula needs to open() the tape drive so that it can read/write it. On both Linux and Solaris, it is possible to open the drive with O_NONBLOCK and get a descriptor that can be used for ioctl() calls and providing there is a tape in the drive, it can be used for read() and write(). On FreeBSD, if there is no tape in the drive, the OS always immediately returns errno=ENXIO "Device not configured". This means that on FreeBSD, if there is no tape in the drive, that drive is totally unusable by Bacula. Another developer, who actually does most of the tape writing routines had two suggestions: 1. Modify Bacula and system dependent code that opens the control device to see if a tape drive is really there or not, and then rewrite the tape driver code to deal with the fact that if you cannot open a device, it may really be there, and you should continue trying to open it between asking the user to mount it. This is clearly possible. 2. Consider implementing something in FreeBSD as exists on at least Linux and Solaris -- i.e. a means to open the drive and get a valid file descriptor. If you read/write/rewind/... a drive opened and there is no tape, it should either return EIO or better ENOMEDIUM. Comments? -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/