On Fri, Aug 12, 2011 at 12:00:45PM -0700, Boaz Harrosh wrote:
> On 08/12/2011 11:39 AM, J. Bruce Fields wrote:
> > On Fri, Aug 12, 2011 at 11:06:51AM -0700, Boaz Harrosh wrote:
> >> I'm confused is this suppose to fix my problem? Because I do not believe
> >> it will. There should not be any error writing a recovery record.
> >>
> >> Please note that the case I have is that the client is a new client. That
> >> loaded after the server loaded and started it's grace. Does a client suppose
> >> to send RECLAIM_COMPLETE in that case too. .i.e send RECLAIM_COMPLETE as first
> >> message after mount?
> >
> > It must send one before it sends any non-reclaim open, yes.
> >
>
> 1. So you are saying the Linux client is broken? How do you test?
Which linux client version, again? See:
"Whenever a client establishes a new client ID and before it does
the first non-reclaim operation that obtains a lock, it MUST
send a RECLAIM_COMPLETE with rca_one_fs set to FALSE, even if
there are no locks to reclaim."
I thought it was only very early ("experimental") 4.1 clients that
omitted RECLAIM_COMPLETE?
Is this actually the deleg reclaim case that Trond mentioned? Could I
see a trace?
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
