On Wed, Sep 28, 2005 at 11:46:37AM -0500, Adam D. Lopresto wrote: > [2] I've actually seen data lost due to this. When drive space is very > limited > (due to, for instance, a user quota) it's often possible to open a new file > (since > there's some space left), but the close fails since too much was written to > it.
Likewise. A certain reputable OS vendor's NFS implementation went multithreaded, with the result that close() was now where the over quota error was reported, rather than the individual writes. Said reputable OS vendor's own C compilers weren't checking close(), so they were caught out by this too. So I think that the problem is real, and is worthy of addressing. I'm not sure of the best approach, or syntax, or defaults. Nicholas Clark
