Re: [PATCH] PUFFS backend allocation (round 3)

[Emmanuel Dreyfus <manu%netbsd.org@localhost>]

On Tue, Oct 28, 2014 at 02:52:36PM +0100, J. Hannken-Illjes wrote:
> NFS allows them and therefore VOP_CLOSE is the last chance to report
> write errors back to the application.

The situation is a bit different: write and fsync call VOP_PUTPAGE
which calls VOP_STRATEGY and forgets about the write error.  The 
write error should be recovered by write and fsync and then cleared:
I do not want to get in in the next write operation: immagine I write
at the end of a file, get EDQUOT, then within an allocated area in the
file, I should not get EDQUOT again.

But what about close? If I am to be reported a write error when calling
close, it should _not_ be cleared as I should get it again if I call
caose again, until the time the write succeeds.

-- 
Emmanuel Dreyfus
manu%netbsd.org@localhost