From xemacs-m  Thu Mar  6 12:51:01 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id MAA22214
	for <xemacs-beta@xemacs.org>; Thu, 6 Mar 1997 12:50:57 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcfst03800; Thu, 6 Mar 1997 13:50:58 -0500 (EST)
Date: Thu, 6 Mar 1997 13:50:58 -0500 (EST)
Message-Id: <QQcfst03800.199703061850@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: [comp.emacs.xemacs] C-x C-s on almost full disk
In-Reply-To: <kigzpwhgf40.fsf@jagor.srce.hr>
References: <kigzpwhgf40.fsf@jagor.srce.hr>
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

 > I just had a serious problem with XEmacs. It appears that when
 > saving a file on a disk that hasn't enough space to store it,
 > XEmacs just stores what it can (yes, the file is truncated),
 > but doesn't report any error.

This kind of problem is almost always due to NFS.  In fact, I've
never tracked a case of it that didn't turn out to be a write
failure on an NFS mounted filesystem.  The problem is that an NFS
server will not always report write failures to the client's
kernel before the client process has closed the descriptor.

The people who say NFS means Not a File System are not kidding.

