From owner-freebsd-current Thu Dec 21 13:04:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA08945 for current-outgoing; Thu, 21 Dec 1995 13:04:46 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA08935 for ; Thu, 21 Dec 1995 13:04:37 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA03866; Thu, 21 Dec 1995 14:05:39 -0700 Date: Thu, 21 Dec 1995 14:05:39 -0700 From: Nate Williams Message-Id: <199512212105.OAA03866@rocky.sri.MT.net> To: Paul Richards Cc: current@FreeBSD.org Subject: Re: Impressions of stability ( was Re: FreeBSD-current-stable ??? ) In-Reply-To: <199512212050.UAA11834@cadair.elsevier.co.uk> References: <199512212050.UAA11834@cadair.elsevier.co.uk> Sender: owner-current@FreeBSD.org Precedence: bulk Paul Richards writes: > If you try and write a file to a nearly full filesystem and that write > fails because the filesytem fills up, the file gets truncated. This is > a very nasty thing to happen. I'm not sure what the actual course of > events are but I'd really like to find some way of preventing it from > happening. I'd be satisfied if I just ended up with part of the file but > losing the whole thing can be really annoying if it's a chapter of your > thesis, which is what once happened to me. This has been the way FreeBSD has worked since day one, and although I believe it would be nice to see this changed, unless someone wants to get down and dirty with the kernel to see how it can be fixed it's not gonna get fixed. :( Nate