Date: Sun, 6 Jun 1999 04:59:26 -0500 (EST) From: Alfred Perlstein <bright@rush.net> To: Tom <tom@uniserve.com> Cc: "Ron 'The InSaNe One' Rosson" <insane@lunatic.oneinsane.net>, michael@alderete.com, freebsd-stable@FreeBSD.ORG Subject: Re: [HELP!] Crashing FreeBSD server with file system corruption Message-ID: <Pine.BSF.3.96.990606045523.9491b-100000@cygnus.rush.net> In-Reply-To: <Pine.BSF.4.02A.9906052157160.7966-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 5 Jun 1999, Tom wrote: > On Sat, 5 Jun 1999, Alfred Perlstein wrote: > > > On Sat, 5 Jun 1999, Ron 'The InSaNe One' Rosson wrote: > > > > > On Sat, Jun 05, 1999 at 10:58:07AM -0700, Michael A. Alderete wrote: > > > > > > > > * The disk subsystem is a SCSI RAID controller from > > > > DPT. It's a PCI card and has 4 drives attached, > > > > configured in a RAID 5 with one drive as a hot > > > > standby. > > > > > > > One possibility could be the DPT. You might want to try a SCSI to SCSI > > > raid solution. Reason why I say this is because a close friend of mine > > > was seeing the same thing with there DPT's moved over to an infortrend <sp?> > > > scsi-scsi solution and the filesystem corruption went away. > > > > We tried for a month to get a DPT controller working with FreeBSD, > > and failed, we tried: > > > > 1) new card > > 2) new drives > > 3) new motherboard > > 4) new cables > > 5) crying > > 6) praying > > ... > > > > Well I really don't want to talk about things past "6" > > Well, I have a 24x7 production with 300+ days of uptime and a DPT > PM334UW card. Since your uptime is 300+ days I'm going to assume you have a very old version of FreeBSD running, one that doesn't have problems with the driver. There's a chance that it's my user error, but when you have 3 people noticing problems with the DPT driver under load with recent versions of FreeBSD, it could mean a problem. It seemed that under hard I/O load it would corrupt data on disk giving me directories that were impossible to delete and forcing me to "reboot -n" to get fsck to fix it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" 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.96.990606045523.9491b-100000>