On Wed, 6 Oct 1999, Peter Jeremy wrote:
> 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_.
Please read more of the thread before replying, the fact of
the matter is that softupdates can crash the system when this
happens, not a mere application, but the entire system can lock up.
> 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).
Which isn't an option unless you dedicate a partition for /tmp
which is pretty wasteful imo.
-Alfred
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
