Date: Tue, 26 Jun 2001 12:27:48 -0700 From: "Kevin Oberman" <oberman@es.net> To: Andrew Reid <andrew.reid@plug.cx> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD and surviving unclean shutdowns Message-ID: <200106261927.f5QJRmc06958@ptavv.es.net> In-Reply-To: Your message of "26 Jun 2001 11:44:08 %2B0930." <993521648.1058.8.camel@percible.alfred.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Andrew Reid <andrew.reid@plug.cx> > Date: 26 Jun 2001 11:44:08 +0930 > Sender: owner-freebsd-questions@FreeBSD.ORG > > While I am resurecting one of my mail servers (which is currently > running Linux) the thought crossed my mind "How would FreeBSD cope with > this situation?" > > This server is running Software-RAID on a (patched for RAID) 2.2 kernel, > and last night, the power went out for about three hours. My UPS only > lasted for 2 of them. > > How does FreeBSD cope with these sort of things? My Cache server took > about an hour-and-a-half of fsck.ext2'ing to come back to a useable > state. Use softupdates. This will both improve the chances of no data loss and will (purportedly) make fsck run faster. See the tunefs man page for how to turn on softupdates on a file system. (Note: you turn it on on a mount point (e.g. /usr), not a partition (/dev/aac0s1e). It is non-volatile. Turn it on for a file system and it will stay on after a reboot. When V5.0 comes out next year, it will do fsck in the background since there is no reason to run fsck on a softupdate file system before starting to use it. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106261927.f5QJRmc06958>