Article View: comp.mail.mh
Article #1964close/fclose error status and NFS file systems
From: Jim Mayer
Date: Fri, 05 Jan 1990 13:46
Date: Fri, 05 Jan 1990 13:46
24 lines
1621 bytes
1621 bytes
Is there a "standard" fix to the following problem? MH (including MH6.6)
while generally pretty good about checking error status returns does not
check the return status from "close" system calls. This almost never causes
trouble when the file is on a locally mounted (4.2 in Sun parlance) file
system. Unfortunately, it is a disaster when using remote (NFS) file systems.
What happens? Well, NFS buffers up requests (write-behind) until it has
about 8K or so of data. If an error occurs during the physical write
(e.g. no space on device) it will not be reported until the next write or
the close.
I would be very interested in locating any patches to this problem.
-- Jim Mayer
Xerox Webster Research Center
Phone: (716) 422-9407 FAX: x2126 800 Phillips Road, 0128-29E
Internet: mayer.wbst128@xerox.com Webster, New York 14580
--
-- Jim Mayer
Xerox Webster Research Center
Phone: (716) 422-9407 FAX: x2126 800 Phillips Road, 0128-29E
Internet: mayer.wbst128@xerox.com Webster, New York 14580
Technical Details
Message-ID:
<284@spot.wbst128.xerox.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!zaphod.mps.ohio-state.edu!sunybcs!uhura.cc.rochester.edu!rochester!spot!mayerShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!zaphod.mps.ohio-state.edu!sunybcs!uhura.cc.rochester.edu!rochester!spot!mayer From: mayer@uffa.uucp (Jim Mayer) Newsgroups: comp.mail.mh Subject: close/fclose error status and NFS file systems Message-ID: <284@spot.wbst128.xerox.com> Date: 5 Jan 90 13:46:20 GMT Sender: news@spot.wbst128.xerox.com Reply-To: mayer@rocksanne.uucp (Jim Mayer) Organization: Xerox Corporation, Webster Research Center Lines: 24