tree a250f2f7f9db1d89abcf39c70d8fe4ae9039a7c8
parent 518776800c094a518ae6d303660b57f1400eb1eb
author Jeff Layton <jlayton@primarydata.com> 1406684264 -0400
committer J. Bruce Fields <bfields@redhat.com> 1406689718 -0400

nfsd: print status when nfsd4_open fails to open file it just created

It's possible for nfsd to fail opening a file that it has just created.
When that happens, we throw a WARN but it doesn't include any info about
the error code. Print the status code to give us a bit more info.

Our QA group hit some of these warnings under some very heavy stress
testing. My suspicion is that they hit the file-max limit, but it's hard
to know for sure. Go ahead and add a -ENFILE mapping to
nfserr_serverfault to make the error more distinct (and correct).

Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>