Date: Wed, 8 Apr 2009 11:24:01 -0600 From: Geoff Fritz <gfritz@gmail.com> To: John Almberg <jalmberg@identry.com> Cc: freebsd-questions@freebsd.org Subject: Re: low-level format before install? Message-ID: <20090408172401.GA76244@dev.null> In-Reply-To: <14CAA4F0-E027-4C28-B53D-A781E8F8CF68@identry.com> References: <13D52068-D184-42D9-AE6C-F095C1283975@identry.com> <E51B1324-35C0-41D1-AFF9-4E7E957B2D29@mac.com> <3A934D4A-1864-401C-8CD8-86B37EB2B183@identry.com> <20090407204242.GD62574@slackbox.xs4all.nl> <14CAA4F0-E027-4C28-B53D-A781E8F8CF68@identry.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 07, 2009 at 05:41:27PM -0400, John Almberg wrote: > Thanks for all the tips. At least I have something to start with. > > The guys in the data center reinstalled FreeBSD (the filesystem was > totally corrupted again), and then ran what they called "SMART test", > which might be smartctl, and said the hard drives look good. > > I am now able to get back in. > > So the system ran fine until I put a load on it with the database > (many transactions a second). This corrupted the file system again. > > So I guess I need to load it enough to produce error messages > (hopefully) but not enough to destroy the file system again. I've had issues with a few hosted servers, and more often than not, it was a bad PSU on the server and/or rack. Assuming that you can't get these folks to run a good hardware diag for you, there are a few things you can do. You can beat up the RAM/cpu with various burn-in programs (I like benchmarks/stream for its simplicity -- you'll need to "make extract", customize, then ,"make install" for your own memory size). You can thrash the disks pretty well with either dd or "badblocks" from sysutils/e2fsprogs, both can be non-destructive. -- Geoff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090408172401.GA76244>