Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@redhat.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Casey Bodley <cbodley@citi.umich.edu>,
	NFS list <linux-nfs@vger.kernel.org>,
	Mi Jinlong <mijinlong@cn.fujitsu.com>,
	Malcolm Locke <malc@wholemeal.co.nz>
Subject: Re: Grace period NEVER ends
Date: Fri, 12 Aug 2011 16:36:06 -0400	[thread overview]
Message-ID: <20110812203606.GL16960@pad.fieldses.org> (raw)
In-Reply-To: <4E45785D.40103@panasas.com>

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.

  reply	other threads:[~2011-08-12 20:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12  0:51 Grace period NEVER ends Boaz Harrosh
2011-08-12  1:14 ` J. Bruce Fields
2011-08-12  1:16 ` Boaz Harrosh
2011-08-12  1:29   ` Boaz Harrosh
2011-08-12  2:15     ` J. Bruce Fields
2011-08-12 14:08       ` Casey Bodley
2011-08-12 14:32         ` J. Bruce Fields
2011-08-12 18:06           ` Boaz Harrosh
2011-08-12 18:39             ` J. Bruce Fields
2011-08-12 19:00               ` Boaz Harrosh
2011-08-12 20:36                 ` J. Bruce Fields [this message]
2011-08-12 20:44                   ` Boaz Harrosh
2011-08-12 20:48                     ` J. Bruce Fields
2011-08-12 19:30           ` Casey Bodley
2011-08-12 20:36           ` Boaz Harrosh
2011-08-12 21:09             ` Boaz Harrosh
2011-08-12 15:52     ` Trond Myklebust
2011-08-12 16:25       ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110812203606.GL16960@pad.fieldses.org \
    --to=bfields@redhat.com \
    --cc=bharrosh@panasas.com \
    --cc=cbodley@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=malc@wholemeal.co.nz \
    --cc=mijinlong@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox