Date: Thu, 28 May 1998 23:33:04 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: tcobb <tcobb@staff.circle.net> Cc: "'Greg Lehey'" <grog@lemis.com>, "'Mike Smith'" <mike@smith.net.au>, "'freebsd-current@freebsd.org'" <freebsd-current@FreeBSD.ORG> Subject: RE: DPT driver fails and panics with Degraded Array Message-ID: <Pine.BSF.3.95.980528233209.5747C-100000@current1.whistle.com> In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC7@freya.circle.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I guess this is really something you want to discuss with simon. I'm sure he will contact you soon He's just finished moving houes and has been out-of-touch fro a few weeks julian On Fri, 29 May 1998, tcobb wrote: > > -----Original Message----- > > From: Greg Lehey [mailto:grog@lemis.com] > > > If you just want to report a bug, use send-pr. That will reach the > > person responsible for it as quickly as possible (consider that a lot > > of us just drop some of the mailing lists when the combined volume > > gets too high). The purpose of sending the message to -CURRRENT > > would be to draw the problem to the attention of other people using > > the software. > > Indeed. And that was the point of sending to freebsd-current. I wanted > anyone using the DPT driver and expecting it to perform appropriately in > critical circumstances to know that it will not do so. I perhaps should > have sent the email to -hackers instead? Or, maybe -scsi, like I did -- > it is a scsi driver problem I'm talking about. > > I chose HA hardware for the particular reason that the server needs to > be *available*. I settled on FreeBSD for all the servers I manage 2.5 > years ago because it was the highest quality OS for Intel architectures. > > > > "Indicators" are that I shouldn't be using FreeBSD for any High > > > Availability or critical operations -- I AM using FreeBSD > > for > 15 live > > > servers. > > > > > > Now, what was your point? > > > > > > Basically, I'd guess Mike is saying "don't use FreeBSD-CURRENT in > > production environments". > > I agree. I wouldn't have done so without provocation. My counterpoint > is that FreeBSD-STABLE is NOT stable, either. Regardless, due to > show-stopper bugs in -stable... > > My choices were: > > 1. Discard FreeBSD completely for this server. > 2. Switch to a -current snapshot. > > I didn't want to do #1, so I spent two weeks rolling a -current snapshot > release for my in-house use, I tested it, and tested it. It works well. > > My posting was really to point to the fact that it appears that the DPT > driver is deficient across ALL releases, not just -current. > > Believe me, I understand the uncharted waters I've entered with my > -current snapshot. The DPT driver failure was the unexpected thing. > > > -Troy Cobb > Circle Net, Inc. > http://www.circle.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980528233209.5747C-100000>