From owner-freebsd-stable Sun Jun 6 2:36:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 4D63B14C94 for ; Sun, 6 Jun 1999 02:36:08 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id EAA25202; Sun, 6 Jun 1999 04:59:27 -0500 (EST) Date: Sun, 6 Jun 1999 04:59:26 -0500 (EST) From: Alfred Perlstein To: Tom Cc: "Ron 'The InSaNe One' Rosson" , michael@alderete.com, freebsd-stable@FreeBSD.ORG Subject: Re: [HELP!] Crashing FreeBSD server with file system corruption In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 > > > 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