From owner-freebsd-bugs Wed Nov 29 6:30:21 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from deneb.healthnet-sl.es (deneb.healthnet-sl.es [213.201.25.69]) by hub.freebsd.org (Postfix) with ESMTP id 4829037B699 for ; Wed, 29 Nov 2000 06:30:18 -0800 (PST) Received: from ntw3 ([213.201.25.94]) by deneb.healthnet-sl.es (8.9.3/8.9.3) with SMTP id PAA73989; Wed, 29 Nov 2000 15:29:02 +0100 (CET) (envelope-from amengual@healthnet.es) Message-ID: <010d01c05a10$a6901190$0400000a@hin> From: "Carlos Amengual" To: "Greg Lehey" Cc: "Soren Schmidt" , References: <200011290755.IAA75175@freebsd.dk> Subject: RE: kern/22086: DMA errors during intensive disk activity on vinum volume Date: Wed, 29 Nov 2000 15:28:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No lack of consideration for Greg's work intended, but as RAID is essentially meant to be used in critical-mission servers, people isn't likely to be willing to play & debug something on which their businesses will depend, especially when hardware controllers (which apparently work) are available. Carlos ----- Mensaje original ----- De: "Soren Schmidt" Para: "Greg Lehey" CC: "Carlos Amengual" ; Enviado: miércoles 29 de noviembre de 2000 8:55 Asunto: Re: kern/22086: DMA errors during intensive disk activity on vinum volume > It seems Greg Lehey wrote: > > > > > > This is an old problem with vinum, somehow vinum manage to trash > > > the ad_request struct between where the ata drives makes it in > > > ad_strategy and when it actually gets used later.. > > > I thought this was fixed at least in -current long ago, but > > > apparently this was either not backported to -stable or the fix > > > was not good enough. > > > > No, the problem went into hiding. It was you who thought it had gone > > away. > > Yes, at a time, but back then we found out that fxp just accelerated > the problem, it did not create it. > > > 1. This config does not include an fxp device, which you had in the > > past blamed for the problems: > > > > > Now, I'm not sure if its vinum or the fxp driver that has a > > > problem, but since others have seen strange problems semilar to > > > this on other type of systems, I'd say it points very much at > > > fxp... The latest fix you put into -current is needed though... > > See above, I provided you with dumps and what not, but it newer > got past that. Since you removed your maintainer bit on vinum it > all went into a halt. In the meantime I have decommisioned all > the vinum boxes I had out there, fortunately all had either > promise or highpoint controllers so they now run ATA RAID's > happily without any problems, so vinum is no longer an issue for > me at least... > > > 2. Robin seems to be able to work through the source code, so this > > time we may be able to catch it. > > More power to you :) > > -Søren > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message