Date: Wed, 6 Oct 1999 10:38:49 +1000 From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> To: Alfred Perlstein <bright@wintelcom.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: make install trick Message-ID: <99Oct6.103524est.40351@border.alcanet.com.au> In-Reply-To: <Pine.BSF.4.05.9910051651210.6368-100000@fw.wintelcom.net> References: <000101bf0f78$fbe58b40$021d85d1@youwant.to> <Pine.BSF.4.05.9910051651210.6368-100000@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-Oct-06 09:55:26 +1000, Alfred Perlstein wrote: >I've seen softupdates nearly eliminate disk io for systems that used >an abmornal amount of temp files, but the fact that it can destabilize >a system worries me greatly. What do you mean by `destabilize'? There are bugs in softupdates which mean that an application may receive ENOSPC when writing to a filesystem even though space on that filesystem has been recently freed. Any application that cannot handle this situation is _broken_. Another option for /tmp - which I forgot last time, and seems to avoid the known problems with MFS and softupdates - it to mount /tmp async. Since you're going to blow it all away on the next reboot anyway, it doesn't really matter if the a crash trashes the FS (which is the major problem with async mounts). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99Oct6.103524est.40351>