Bug 52612

Summary: [PATCH] close() can return undocumented ENOSPC
Product: Documentation Reporter: marcolz <marcolz>
Component: Books & ArticlesAssignee: Tom Rhodes <trhodes>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description marcolz 2003-05-23 15:10:02 UTC 
	On cached for example NFS, close can return ENOSPC, indicating
	that it could not correctly write pending flushes to disk. It
	would be nice to have this documented. Also, the paragraph about
	why you should use close() yourself, made me wonder what kind of
	programming we were trying to promote here...

Fix: Patch follows:

How-To-Repeat: 	NFS mount a dir, write enough to it (at least 4 Mb in my case,
	it's porbably some buffersize issue), then close() the file and
	see ENOSPC returned.
Comment 1 Tom Rhodes freebsd_committer freebsd_triage 2003-06-09 18:16:52 UTC 
Responsible Changed
From-To: freebsd-doc->trhodes

Take this PR.
Comment 2 Tom Rhodes freebsd_committer freebsd_triage 2003-06-13 23:41:35 UTC 
State Changed
From-To: open->patched

Partial commit.  I'm not sure about the first hunk, though, and would 
like some review before I commit it.
Comment 3 Tom Rhodes freebsd_committer freebsd_triage 2003-08-10 06:31:04 UTC 
State Changed
From-To: patched->closed

MFC complete, thanks for the submission.