All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
To: NFS list <linux-nfs@vger.kernel.org>,
	Steve Dickson <SteveD@redhat.com>,
	"J. Bruce Fields" <bfields@fieldses.org>
Subject: pNFS read/write behavior change in 2.6.39
Date: Tue, 26 Apr 2011 16:03:56 +0200	[thread overview]
Message-ID: <4DB6D0CC.4050601@desy.de> (raw)


I run 2.6.39-0.rc4.git2.0 build for fedora-16 build by redhat.
Probably Steve and Bruce can comment on the patch set.

My observation is that state id provided by client on read to
DS dit not contain correct stateid:

struct stateid4 {
         uint32_t        seqid;
         opaque          other[12];
};

The seqid equals to zero when client send it to DS which is not the
value returned on OPEN.

The problem is not observed with

ae7441fa120ff35b40b4dab167645907a9da1dab

from Bennys tree  as well as with frdora 15 builds from Steve.
With
Regards,
    Tigran.

             reply	other threads:[~2011-04-26 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 14:03 Tigran Mkrtchyan [this message]
2011-04-26 14:29 ` pNFS read/write behavior change in 2.6.39 Trond Myklebust
2011-04-26 14:37   ` Tigran Mkrtchyan
2011-04-26 14:40     ` Tigran Mkrtchyan
2011-04-26 16:52     ` Trond Myklebust

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=4DB6D0CC.4050601@desy.de \
    --to=tigran.mkrtchyan@desy.de \
    --cc=SteveD@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    /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.