Date: Fri, 6 Dec 2002 15:12:27 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Kirk McKusick <mckusick@beastie.mckusick.com> Cc: Archie Cobbs <archie@dellroad.org>, freebsd-current@FreeBSD.ORG Subject: Re: backgroud fsck is still locking up system (fwd) Message-ID: <20021206211225.GA29693@dan.emsphone.com> In-Reply-To: <200212062000.gB6K0659093727@beastie.mckusick.com> References: <200212061928.gB6JSqn0065389@arch20m.dellroad.org> <200212062000.gB6K0659093727@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Dec 06), Kirk McKusick said: > The main reason for not using soft updates on the root filesystem was > because of the delay between removing files and having the space show > up. The result was that world installs on the root filesystem often > failed if the root was nearly full (as is so often the case). That > problem has now been fixed in 5.0 with a callback to soft updates if > a filesystem full error is about to be generated. When called back, > soft updates expedites the freeing of space so that the new > allocation can succeed. So, the primary reason for not using soft > updates on the root is now fixed. If however, mainline editors are > not doing fsync's, then there is still a good reason not to use soft > updates on the root filesystem. /usr/bin/install does not fsync. One of my three foot-shootings involved installing a new /sbin/init and hitting the power switch. -- Dan Nelson dnelson@allantgroup.com 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?20021206211225.GA29693>