nfsd4: fix failure to end nfsd4 grace period
authorBoaz Harrosh <bharrosh@panasas.com>
Sat, 13 Aug 2011 00:30:12 +0000 (17:30 -0700)
committerJ. Bruce Fields <bfields@redhat.com>
Sat, 27 Aug 2011 18:21:21 +0000 (14:21 -0400)
commit6577aac01f00636c16cd583c30bd4dedf18475d5
treecd7aef18e8be2615179638c036172958b0597252
parent48483bf23a568f3ef4cc7ad2c8f1a082f10ad0e7
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>
fs/nfsd/nfs4recover.c