From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 1 04:53:50 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D097937B401; Sun, 1 Jun 2003 04:53:50 -0700 (PDT) Received: from silver.he.iki.fi (silver.he.iki.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F91143FAF; Sun, 1 Jun 2003 04:51:09 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (localhost.he.iki.fi [127.0.0.1]) by silver.he.iki.fi (8.12.9/8.11.4) with ESMTP id h51Bp7k8003853; Sun, 1 Jun 2003 14:51:08 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <3ED9E8AB.5060106@he.iki.fi> Date: Sun, 01 Jun 2003 14:51:07 +0300 From: Petri Helenius User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030501 X-Accept-Language: English [en],Finnish [fi] MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: raidframe X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 11:53:51 -0000 Is there anyone actually successfully using raidframe and if yes, what kind of hardware? Same question goes for any recent SCSI RAID controllers supported by FreeBSD. I admit not having tried all combinations but it seems that using anything else than simple ahc scsi stuff results in kernel panic with 5.x. Pete From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 1 05:25:10 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7984337B401; Sun, 1 Jun 2003 05:25:10 -0700 (PDT) Received: from grogged.dyndns.org (c-66-41-94-114.mn.client2.attbi.com [66.41.94.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id B685A43FE1; Sun, 1 Jun 2003 05:22:29 -0700 (PDT) (envelope-from matt@grogged.dyndns.org) Received: by grogged.dyndns.org (Postfix, from userid 1001) id 060B216809; Sun, 1 Jun 2003 07:13:00 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by grogged.dyndns.org (Postfix) with ESMTP id EB3C3D23C; Sun, 1 Jun 2003 07:13:00 -0500 (CDT) Date: Sun, 1 Jun 2003 07:13:00 -0500 (CDT) From: matt To: Petri Helenius In-Reply-To: <3ED9E8AB.5060106@he.iki.fi> Message-ID: <20030601071231.G76837-100000@grogged.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: raidframe X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 12:25:11 -0000 I'm using a Ami MegaRaid 1500 in 5.x without any issues. -m On Sun, 1 Jun 2003, Petri Helenius wrote: > > Is there anyone actually successfully using raidframe and if yes, what kind > of hardware? > > Same question goes for any recent SCSI RAID controllers supported > by FreeBSD. > > I admit not having tried all combinations but it seems that using anything > else than simple ahc scsi stuff results in kernel panic with 5.x. > > Pete > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 1 09:27:23 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 564BF37B401 for ; Sun, 1 Jun 2003 09:27:23 -0700 (PDT) Received: from hub.org (hub.org [64.117.225.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id CED2743FA3 for ; Sun, 1 Jun 2003 09:27:22 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from hub.org (unknown [64.117.225.220]) by hub.org (Postfix) with ESMTP id 1B6AA6BA75E; Sun, 1 Jun 2003 13:27:21 -0300 (ADT) Date: Sun, 1 Jun 2003 13:27:21 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20030601131404.P6572@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Scott Long Subject: Critical bug in Adaptec(aac) driver ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 16:27:23 -0000 As those on this list will have seen over the past few months, I have a server that had (past tense) an Adaptec 2120s controller in her that was giving alot of grief ... about 3 weeks ago, the server it was in *really* blew up ... one drive was reported as down (in a RAID5 array), and when we tried to bring it back up, a second drive started to "fail" ... I got the techs to shut her down, and literally rushed to the remote location to see if there was anything that I could do to at least recover the data ... When I got there to bring it back up, the server reported that a 3rd drive had failed ... and within a few hours, a 4th drive failed ... the result being that we lost all of the data on that server, which turned out to be quite painful to recover ... While down there, we replaced the Adaptec controller with an Intel one, reformatted the exact same drives, in the exact same chassis, and she's been running fine since ... On my trip back, I had a chat with a friend that does development work in the Linux world, and who had had that server previous to myself, and apparently there is a "known bug" in Linux that he says sounds exactly like what I experienced (they hit it right in the middle of developing on that box) and that there are apparently two Linux kernel patches that they had to apply (after rebuilding from scratch) to correct the problem ... The way he explained the problem to me, he made it sound like the kernel driver was interacting with the BIOs and causing some corruption ... not sure at what level, but since trying to swap in a new controller didn't restore things, I'm suspecting at the hard drive level ... ? Scott, while down there, I tried just about everything I could think to ... we replaced the SCSI cable, put the drives/controller into a second identical chassis, swap host controller cards themselves (I had brought spares) ... and that server, as I mentioned, is currently running quite happily with an Intel host controller in it :( So, unless the same "failure" was hitting two host controllers, hardware failure doesn't seem to have been the cause ... From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 1 10:38:45 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 407BA37B404 for ; Sun, 1 Jun 2003 10:38:45 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75D0E43F93 for ; Sun, 1 Jun 2003 10:38:44 -0700 (PDT) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h51HXmZ28839; Sun, 1 Jun 2003 10:33:48 -0700 Received: from btc.adaptec.com (hollin.btc.adaptec.com [10.100.253.56]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id KAA22298; Sun, 1 Jun 2003 10:38:42 -0700 (PDT) Message-ID: <3EDA3982.5040202@btc.adaptec.com> Date: Sun, 01 Jun 2003 11:36:02 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Marc G. Fournier" References: <20030601131404.P6572@hub.org> In-Reply-To: <20030601131404.P6572@hub.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: Critical bug in Adaptec(aac) driver ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 17:38:45 -0000 Marc G. Fournier wrote: > As those on this list will have seen over the past few months, I have a > server that had (past tense) an Adaptec 2120s controller in her that was > giving alot of grief ... about 3 weeks ago, the server it was in *really* > blew up ... one drive was reported as down (in a RAID5 array), and when we > tried to bring it back up, a second drive started to "fail" ... I got the > techs to shut her down, and literally rushed to the remote location to see > if there was anything that I could do to at least recover the data ... > > When I got there to bring it back up, the server reported that a 3rd drive > had failed ... and within a few hours, a 4th drive failed ... the result > being that we lost all of the data on that server, which turned out to be > quite painful to recover ... > > While down there, we replaced the Adaptec controller with an Intel one, > reformatted the exact same drives, in the exact same chassis, and she's > been running fine since ... > > On my trip back, I had a chat with a friend that does development work in > the Linux world, and who had had that server previous to myself, and > apparently there is a "known bug" in Linux that he says sounds exactly > like what I experienced (they hit it right in the middle of developing on > that box) and that there are apparently two Linux kernel patches that they > had to apply (after rebuilding from scratch) to correct the problem ... > > The way he explained the problem to me, he made it sound like the kernel > driver was interacting with the BIOs and causing some corruption ... not > sure at what level, but since trying to swap in a new controller didn't > restore things, I'm suspecting at the hard drive level ... ? > > Scott, while down there, I tried just about everything I could think to > ... we replaced the SCSI cable, put the drives/controller into a second > identical chassis, swap host controller cards themselves (I had brought > spares) ... and that server, as I mentioned, is currently running quite > happily with an Intel host controller in it :( So, unless the same > "failure" was hitting two host controllers, hardware failure doesn't seem > to have been the cause ... > I understand your frustration and wish there was more I could do to help. Please send me whatever information that you have. Scott From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 1 10:45:24 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8684037B401 for ; Sun, 1 Jun 2003 10:45:24 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0876143F75 for ; Sun, 1 Jun 2003 10:45:23 -0700 (PDT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) by srv1.cosmo-project.de (8.12.9/8.12.9) with ESMTP id h51HjJrN055503 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Jun 2003 19:45:21 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost)h51HjIOf055502 for freebsd-scsi@FreeBSD.org; Sun, 1 Jun 2003 19:45:18 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.12.9/8.12.9) with ESMTP id h51HiIJE039756 for ; Sun, 1 Jun 2003 19:44:23 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.12.9/8.12.9/Submit) id h51HiI1l039755 for freebsd-scsi@FreeBSD.org; Sun, 1 Jun 2003 19:44:18 +0200 (CEST) Date: Sun, 1 Jun 2003 19:44:18 +0200 From: Andreas Klemm To: freebsd-scsi@FreeBSD.org Message-ID: <20030601174418.GA39708@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Operating-System: FreeBSD 5.1-RC X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.4i Subject: Supported Controller under FreeBSD for Sun Storedge A5000, FC-AL ? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 17:45:24 -0000 Hi, q: is there a PCI controller available for FreeBSD 4.x and 5.x which is capable to connect to a Sun Storedge A5000 ? Which FreeBSD driver would it be, that supports this card ? I found this article: http://www.sunhelp.org/pipermail/rescue/2002-June/058045.html But I never heard of an Interphase 5526 PCI controller. Which FreeBSD driver would support it ? Here a example storedge offer on eBay: http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&category=3D8074&item=3D3026979= 541&rd=3D1 Best regards Andreas /// --=20 Andreas Klemm http://www.64bits.de http://www.apsfilter.org/ http://people.FreeBSD.ORG/~andreas From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 1 10:54:46 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DF5B37B401 for ; Sun, 1 Jun 2003 10:54:46 -0700 (PDT) Received: from matou.sibbald.com (matou.sibbald.com [195.202.201.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 621F043F85 for ; Sun, 1 Jun 2003 10:54:44 -0700 (PDT) (envelope-from kern@sibbald.com) Received: from [192.168.68.112] (rufus [192.168.68.112]) by matou.sibbald.com (8.11.6/8.11.6) with ESMTP id h51Hsfv01938 for ; Sun, 1 Jun 2003 19:54:42 +0200 From: Kern Sibbald To: freebsd-scsi@freebsd.org Content-Type: text/plain Organization: Message-Id: <1054490081.1582.1685.camel@rufus> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 01 Jun 2003 19:54:41 +0200 Content-Transfer-Encoding: 7bit Subject: SCSI tape data loss X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 17:54:46 -0000 Hello, I'm the author of a GPL'ed network backup program called Bacula (www.bacula.org). For the last three years, it has been working flawlessly on Solaris and Linux systems. When users attempted to use it recently on FreeBSD, it did not work. I subsequently modified Bacula so that it would work on FreeBSD -- basically, I had to program around some important differences in the way FreeBSD handles EOFs compared to Solaris and Linux. At some point in the future, I would like to discuss the problems I had in detail, if that interests you. However, more recently Dan Langille did some extensive testing writing a 6GB file to six tapes. This brought out additional problems of the driver "freezing" the tape, which I believe I have also programmed around, but worst (and the main reason for this email), Dan discovered that Bacula did not correctly read back the data that was "supposedly" written to the tape. We've now worked on this problem for several weeks, and I believe we have now isolated the problem (data loss) to occur when the end of medium is reached. We have now confirmed that Bacula correctly wrote to the tape, but when it was read back 13 blocks of 64512 bytes were missing. Below, I have listed in pseudo-language what Bacula was doing. Each write with the exception of the first block on the second tape is 64512 bytes: first tape mounted write(block 1) ... write(block 1554); write(block 1555); <=== block lost ... <=== blocks lost write(block 1567); <=== block lost write(block 1568) failed because of EOM detected ioctl(MTIOCERRSTAT); ioctl(MTWEOF); ioctl(MTWEOF); ioctl(MTBSF); ioctl(MTBSF); ioctl(MTBSR); read() returned 0 bytes. ioctl(MTREW); close() new tape mounted. write(block 1); Tape pre-label write(block 1 again); ioctl(MTREW); read(block1); ioctl(MTREW); write(block 1); Tape label write(block 1568); block not written to previous tape. I have verified that Bacula did successfully write 1567 blocks to the first tape, but in reading back the tape, blocks 1555-1567 are not on the tape. Now, the big question is: what caused the loss of those blocks? The most likely causes I can think of are: 1. Bacula is doing something (e.g. MTIOCERRSTAT, or the MTBSF) to cause the data to be lost. If this is the case, it is something specific to FreeBSD since this sequence of commands works on both Solaris and Linux (except that MTIOCERRSTAT is MTIOCLRERR on those systems). 2. The SCSI driver is doing asynchronous writes (very bad) and the End of Medium is not sent to Bacula until many writes after the end of the tape. 3. The SCSI driver has some sort of bug that causes buffers to be lost. There may be other possible reasons that I am unaware of at this moment. Can you shed any light on this problem? If you have any questions concerning the hardware, Dan (dan@langille.com) will be able to provide the answers. Best regards, Kern PS: I am not subscribed to the list so please copy me directly. From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 1 11:32:38 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03CF737B418 for ; Sun, 1 Jun 2003 11:32:38 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id D025C43F93 for ; Sun, 1 Jun 2003 11:32:36 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 2CBA33F4F; Sun, 1 Jun 2003 14:32:36 -0400 (EDT) From: "Dan Langille" To: freebsd-scsi@freebsd.org Date: Sun, 01 Jun 2003 14:32:36 -0400 MIME-Version: 1.0 Message-ID: <3EDA0E84.15066.C424E3B1@localhost> Priority: normal In-reply-to: <1054490081.1582.1685.camel@rufus> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: Kern Sibbald Subject: Re: SCSI tape data loss X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 18:32:38 -0000 On 1 Jun 2003 at 19:54, Kern Sibbald wrote: > If you have any questions concerning the hardware, Dan > (dan@langille.com) will be able to provide the answers. The box is running 4.8-RC FreeBSD 4.8-RC #9: Fri Apr 4 09:15:39 EST 2003 although it may be from a cvsup done much earlier thatn Apr 4. The tape drive is a Archive Python p4586np: http://www.seagate.com/support/tape/specs/dds/p4586np.html The SCSI card is an Adaptec 2940. $ dmesg Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RC #9: Fri Apr 4 09:15:39 EST 2003 root@Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RC #9: Fri Apr 4 09:15:39 EST 2003 root@undef.example.org:/usr/obj/usr/src/sys/UNDEF Timecounter "i8254" frequency 1193182 Hz CPU: AMD Duron(tm) Processor (901.60-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x631 Stepping = 1 Features=0x183f9ff AMD Features=0xc0440000 real memory = 402587648 (393152K bytes) config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 386621440 (377560K bytes) Preloaded elf kernel "kernel" at 0xc04b3000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04b309c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 5 entries at 0xc00fdf20 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 5 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd800-0xd81f irq 5 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: (vendor=0x1106, dev=0x3057) at 7.4 ahc0: port 0xe000-0xe0ff mem 0xdb000000- 0xdb000fff irq 11 at device 9.0 on pci0 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs rl0: port 0xe400-0xe4ff mem 0xdb001000- 0xdb0010ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:50:fc:50:56:88 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: on motherboard pci2: on pcib1 orm0: