Date: Wed, 6 Dec 2000 12:30:09 +0000 From: Josef Karthauser <joe@tao.org.uk> To: Carlos Amengual <amengual@healthnet.es> Cc: Greg Lehey <grog@lemis.com>, Soren Schmidt <sos@freebsd.dk>, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/22086: DMA errors during intensive disk activity on vinum volume Message-ID: <20001206123009.F79990@bsdi.com> In-Reply-To: <010d01c05a10$a6901190$0400000a@hin>; from amengual@healthnet.es on Wed, Nov 29, 2000 at 03:28:26PM %2B0100 References: <200011290755.IAA75175@freebsd.dk> <010d01c05a10$a6901190$0400000a@hin>
next in thread | previous in thread | raw e-mail | index | archive | help
I sent Greg a large amount of debug that it took me a week collection with respect to this problem. Did you ever get anywhere with this Greg? I never got a response from you! Joe On Wed, Nov 29, 2000 at 03:28:26PM +0100, Carlos Amengual wrote: > 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" <sos@freebsd.dk> > Para: "Greg Lehey" <grog@lemis.com> > CC: "Carlos Amengual" <webmaster@healthnet-sl.es>; <freebsd-bugs@FreeBSD.ORG> > 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 > -- Josef Karthauser [joe@FreeBSD.org, joe@tao.org.uk] ......... FreeBSD: The power to change the world ........ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001206123009.F79990>