All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Coddington <bcodding@redhat.com>
To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
Cc: Olga Kornievskaia <aglo@umich.edu>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: 4.0 NFS client in infinite loop in state recovery after getting BAD_STATEID
Date: Fri, 8 May 2015 09:08:03 -0400 (EDT)	[thread overview]
Message-ID: <alpine.OSX.2.19.9992.1505080906070.656@planck.local> (raw)
In-Reply-To: <752919938.1601268.1431090048609.JavaMail.zimbra@desy.de>

Yes, I've done that, and the client's behavior correctly cycles through
OPEN, then READ with the new stateid.  Are you able to create what Olga's
talking about -- which is (I believe) a loop of just OPENs?

Ben

On Fri, 8 May 2015, Mkrtchyan, Tigran wrote:

> Hi Ben,
>
> probably you can simulate, as Olga has suggested, with fault injection.
> I can I can prepare a snadalone version of your server, which returns
> BAD_STATEID on any IO request.
>
> Tigran.
>
> ----- Original Message -----
> > From: "Benjamin Coddington" <bcodding@redhat.com>
> > To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
> > Cc: "Olga Kornievskaia" <aglo@umich.edu>, "Trond Myklebust" <trond.myklebust@primarydata.com>, "linux-nfs"
> > <linux-nfs@vger.kernel.org>
> > Sent: Friday, May 8, 2015 2:25:19 PM
> > Subject: Re: 4.0 NFS client in infinite loop in state recovery after getting BAD_STATEID
>
> > On Fri, 8 May 2015, Mkrtchyan, Tigran wrote:
> >
> >> Hi Olga,
> >>
> >> I believe we see the same infinite loop without delegation with RHEL6/7
> >> kernels, but without delegation being involved. Currently, on the server
> >> side, if client looping is detected, we return RESOURCE. This breaks the
> >> loop and application gets an IO error.
> >>
> >> Your fix is only covers the delegation case isn't it?
> >>
> >> Tigran.
> >
> > Tigran, do you have a BZ or can you tell me how to reproduce this?
> >
> > Ben
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-05-08 13:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 17:04 4.0 NFS client in infinite loop in state recovery after getting BAD_STATEID Olga Kornievskaia
2015-05-08  8:48 ` Mkrtchyan, Tigran
2015-05-08 12:25   ` Benjamin Coddington
2015-05-08 13:00     ` Mkrtchyan, Tigran
2015-05-08 13:08       ` Benjamin Coddington [this message]
2015-05-08 13:13         ` Mkrtchyan, Tigran
2015-05-08 15:18           ` Olga Kornievskaia
2015-05-08 15:29             ` Benjamin Coddington
2015-05-15 15:52 ` Olga Kornievskaia
2015-05-29 13:44 ` Benjamin Coddington
2015-05-29 16:51   ` Olga Kornievskaia
2015-05-29 17:21     ` Olga Kornievskaia
2015-06-03 15:51       ` Benjamin Coddington

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=alpine.OSX.2.19.9992.1505080906070.656@planck.local \
    --to=bcodding@redhat.com \
    --cc=aglo@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    --cc=trond.myklebust@primarydata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.