From: Benny Halevy <bhalevy@panasas.com>
To: Sandeep Joshi <sjoshi@bluearc.com>
Cc: linux-nfs@vger.kernel.org, NFSv4 <nfsv4@ietf.org>
Subject: Re: 4.1 client - LAYOUTCOMMIT
Date: Tue, 06 Jul 2010 16:20:33 +0300 [thread overview]
Message-ID: <4C332DA1.60204@panasas.com> (raw)
In-Reply-To: <A062FCC8662DA848949F7C3046B9BEAE01F3A6ED@us-email.terastack.bluearc.com>
On Jul. 02, 2010, 2:47 +0300, "Sandeep Joshi" <sjoshi@bluearc.com> wrote:
>
> As per specification value of newoffset4_u.no_offset should be less than or equal to NFS4_MAXFILEOFF.
> But, I observe it to be NFS4_MAXFILELEN.
No.
The last offset the client can access is NFS4_MAXFILEOFF.
Writing a single byte in NFS4_MAXFILEOFF will result in a file
with length NFS4_MAXFILELEN but the loca_last_write_offset
in this case is NFS4_MAXFILEOFF.
Benny
>
>
> regards,
>
> Sandeep
prev parent reply other threads:[~2010-07-06 13:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 23:47 4.1 client - LAYOUTCOMMIT Sandeep Joshi
2010-07-02 0:07 ` 4.1 client - LAYOUTCOMMIT & close Sandeep Joshi
[not found] ` <A062FCC8662DA848949F7C3046B9BEAE01F3A6EE-e1HlL03umel79urLq6li5IWksG4c/lV9Sp/tIRYA5EM@public.gmane.org>
2010-07-02 15:41 ` Andy Adamson
2010-07-02 17:08 ` 4.1 client - LAYOUTCOMMIT & close Suchit Kaura
[not found] ` <loom.20100702T190300-538-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-07-06 13:12 ` Andy Adamson
2010-07-06 13:23 ` Benny Halevy
2010-07-02 21:46 ` 4.1 client - LAYOUTCOMMIT & close Daniel.Muntz
2010-07-06 13:35 ` Benny Halevy
2010-07-06 13:37 ` Andy Adamson
2010-07-06 14:04 ` Boaz Harrosh
2010-07-06 19:20 ` Daniel.Muntz
2010-07-06 20:40 ` Trond Myklebust
2010-07-06 22:50 ` Daniel.Muntz
2010-07-06 23:23 ` Trond Myklebust
2010-07-07 12:05 ` Benny Halevy
2010-07-07 13:06 ` Trond Myklebust
2010-07-07 13:18 ` [nfsv4] " Trond Myklebust
2010-07-07 13:51 ` Benny Halevy
2010-07-07 14:03 ` Trond Myklebust
2010-07-07 17:45 ` Dean Hildebrand
2010-07-07 20:39 ` Daniel.Muntz
2010-07-07 21:01 ` Trond Myklebust
2010-07-07 22:04 ` Noveck_David
2010-07-07 22:27 ` Trond Myklebust
2010-07-07 22:44 ` david.black
2010-07-07 22:52 ` Trond Myklebust
2010-07-07 23:09 ` Trond Myklebust
[not found] ` <1278544497.15524.17.camel@heimdal.trondhje! m .org>
[not found] ` < 4C35F5E3.3000604@panasas.com>
2010-07-07 23:14 ` Trond Myklebust
2010-07-08 15:59 ` Benny Halevy
2010-07-08 20:30 ` [nfsv4] " david.black
2010-07-08 21:16 ` Trond Myklebust
2010-07-08 23:51 ` Daniel.Muntz
[not found] ` <1278623771.13551.54.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-07-09 0:03 ` [nfsv4] " Sandeep Joshi
2010-07-08 22:12 ` sfaibish
2010-07-08 23:01 ` Tom Haynes
2010-07-08 23:57 ` sfaibish
2010-07-09 0:41 ` [nfsv4] " Trond Myklebust
2010-07-06 13:20 ` Benny Halevy [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=4C332DA1.60204@panasas.com \
--to=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.org \
--cc=sjoshi@bluearc.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).