From owner-freebsd-stable Sat Jun 5 11:35:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 17F3414EBD; Sat, 5 Jun 1999 11:35:30 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2221.bossig.com [208.26.242.221]) by revolution.3-cities.com (8.9.3/8.9.3) with ESMTP id LAA10289; Sat, 5 Jun 1999 11:35:27 -0700 (PDT) Message-ID: <37596DB5.6AC67C88@3-cities.com> Date: Sat, 05 Jun 1999 11:34:29 -0700 From: Kent Stewart Reply-To: kstewart@3-cities.com Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: alderete@yahoo.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [HELP!] Crashing FreeBSD 3.1 Server with file system corruption References: <19990605180849.23964.rocketmail@web125.yahoomail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stop clogging everyones mail boxes. One request is all you need. You have to wait until someone that knows about your type of problem reads their mail. Kent "Michael A. Alderete" wrote: > > I have a FreeBSD-based web/ftp server that is crashing > regularly, and the crashes are causing (caused > by?)filesystem corruption. > > I'm suspecting (and hoping) that it's just a > configuration problem, or a known bug with an easy > workaround. I'd hate to learn that there was something > inherently wrong here! > > Here are the details, hopefully someone will recognize > the issue: > > * The server hardware is an Intel N440BX motherboard, > with two Intel Pentium III 450 processors. 256 megs of > RAM. Built-in graphics, and a PCI NE2000 Ethernet card > (the built-in EtherExpress interface wouldn't work for > me, another story, another time). > > * 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. > > * FreeBSD is version 3.1-STABLE-05051999, with the > kernel recompiled for SMP support and MAXUSERS=256. > > * The server worked fine for me as I was installing > and upgrading it, adding and compiling additional > software, uploading megabytes of data to the ftp > directories, etc. > > * The server also had no difficulties when I sent out > a company-internal e-mail with a request to bang on > it. That's a load of about 30 users at any give > time(http only, though). > > * We put it into production use as our main web server > on Wednesday night. It handled quite a high load as > people checked out the new site design. > > * Thursday night was the first crash, we don't know > what caused it. The server rebooted, but fsck failed > on /home, and so it didn't come up automatically. > Manually running fsck fixed the errors, with a few > files recovered to lost+found. > > * The next morning while examining the files in > lost+found, doing a cp of one of the files, the server > crashed again. This time it rebooted itself, found no > file system problems, and came up. > > * Last night (Saturday at 5:30am, actually) it failed > again. This time there are file system errors on /usr > and /home. fsck fixed the problems on /usr and most of > them on /home, but now we're getting an error about a > bad sector. /home obviously refuses to mount. > > Anything known about problems in FreeBSD-STABLE with > SMP configurations and RAID sub-systems? Or other > obvious (or subtle) problems? > > Thanks much! > Michael > === > > --- > Michael A. Alderete > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message