summaryrefslogtreecommitdiff
path: root/fs/nfsd/nfs4state.c
diff options
context:
space:
mode:
authorBoaz Harrosh <bharrosh@panasas.com>2011-08-13 00:30:12 (GMT)
committerJ. Bruce Fields <bfields@redhat.com>2011-08-27 18:21:21 (GMT)
commit6577aac01f00636c16cd583c30bd4dedf18475d5 (patch)
treecd7aef18e8be2615179638c036172958b0597252 /fs/nfsd/nfs4state.c
parent48483bf23a568f3ef4cc7ad2c8f1a082f10ad0e7 (diff)
downloadlinux-fsl-qoriq-6577aac01f00636c16cd583c30bd4dedf18475d5.tar.xz
nfsd4: fix failure to end nfsd4 grace period
Even if we fail to write a recovery record, we should still mark the client as having acquired its first state. Otherwise we leave 4.1 clients with indefinite ERR_GRACE returns. However, an inability to write stable storage records may cause failures of reboot recovery, and the problem should still be brought to the server administrator's attention. So, make sure the error is logged. These errors shouldn't normally be triggered on a corectly functioning server--this isn't a case where a misconfigured client could spam the logs. Signed-off-by: Boaz Harrosh <bharrosh@panasas.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd/nfs4state.c')
0 files changed, 0 insertions, 0 deletions