Searched hist:b3fbfe0e7a1d88e3cbaa282c5f6fc50e8c67448c (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/fs/nfsd/ |
| H A D | nfsproc.c | diff b3fbfe0e7a1d88e3cbaa282c5f6fc50e8c67448c Tue Jul 29 20:37:44 CDT 2014 Jeff Layton <jlayton@primarydata.com> 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>
|
| H A D | nfs4proc.c | diff b3fbfe0e7a1d88e3cbaa282c5f6fc50e8c67448c Tue Jul 29 20:37:44 CDT 2014 Jeff Layton <jlayton@primarydata.com> 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>
|