From: Fred Isaman <iisaman@netapp.com>
To: vishal.thanki@gmail.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: LAYOUTGET failure handling
Date: Fri, 23 Dec 2011 09:26:15 -0500 [thread overview]
Message-ID: <CADnza47Xo2Xt1zXiaAxoNWcwGDGi40a6jUhzFJkKu+oe-7PJGg@mail.gmail.com> (raw)
In-Reply-To: <CAC3a_SD609RTOaCzh4g+Ukng8Z7+oQn+r-vEBMPDPMU7nxPWRA@mail.gmail.com>
On Fri, Dec 23, 2011 at 6:21 AM, Vishal Thanki <vishalthanki@gmail.com> wrote:
> 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?
>
Yes. The client asked for a layout. The server said no. So the
client fell back to using standard io to the MDS.
Right now this is basically how the linux client responds to almost all errors.
Fred
> 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
prev parent reply other threads:[~2011-12-23 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 11:21 LAYOUTGET failure handling Vishal Thanki
2011-12-23 11:39 ` Vishal Thanki
2011-12-23 14:26 ` Fred Isaman [this message]
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=CADnza47Xo2Xt1zXiaAxoNWcwGDGi40a6jUhzFJkKu+oe-7PJGg@mail.gmail.com \
--to=iisaman@netapp.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).