linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vishal Thanki <vishalthanki@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: LAYOUTGET failure handling
Date: Fri, 23 Dec 2011 16:51:46 +0530	[thread overview]
Message-ID: <CAC3a_SD609RTOaCzh4g+Ukng8Z7+oQn+r-vEBMPDPMU7nxPWRA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Hi,

I am learning NFS (and pNFS) and not much familiar with its
implementation in Linux kernel. I have a question on the LAYOUTGET
operation.

I have a pNFS server setup which fakes most of the pNFS operations.
The "layout_get" implementation simply returns "-ENOENT". I am not
sure how this should be treated on the pNFS client side. In my
experiment, I am mounting the pNFS server and trying to read a file
(using "cat"). On wireshark trace (attached with the mail), I could
see that LAYOUTGET fails with NFS4ERR_BADLAYOUT error, but afterwards
I see the READ request from client and it is handled gracefully (and I
can see the contents of the file). Is this appropriate behavior?

I am using RHEL6.1 (with pNFS patch for kernel 2.6.32 applied) on
server, and client is RHEL6.1 stock kernel.

I am sorry if this is not the appropriate forum for such kind of
questions, and pardon my ignorance/lack of knowledge in the domain.

Thanks,
Vishal

[-- Attachment #2: pnfs_layoutget_failure.cap --]
[-- Type: application/octet-stream, Size: 27140 bytes --]

             reply	other threads:[~2011-12-23 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 11:21 Vishal Thanki [this message]
2011-12-23 11:39 ` LAYOUTGET failure handling Vishal Thanki
2011-12-23 14:26 ` Fred Isaman

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=CAC3a_SD609RTOaCzh4g+Ukng8Z7+oQn+r-vEBMPDPMU7nxPWRA@mail.gmail.com \
    --to=vishalthanki@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=vishal.thanki@gmail.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;
as well as URLs for NNTP newsgroup(s).