All of lore.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: silent truncation for large file offsets
Date: Mon, 8 Feb 2016 14:30:12 -0500	[thread overview]
Message-ID: <20160208193012.GG17411@fieldses.org> (raw)
In-Reply-To: <20160208183328.GA29982@infradead.org>

On Mon, Feb 08, 2016 at 10:33:28AM -0800, Christoph Hellwig wrote:
> >From a Linux client to a Linux server (in fact the same system in this
> example), NFSv4.1, XFS file system:
> 
> root@vm:~/xfstests# truncate --size 9223372036854775807 /mnt/nfs1/test
> root@vm:~/xfstests# ls -l /mnt/nfs1/test
> -rw-r--r-- 1 root root 9223372036854775806 Feb  8 18:30 /mnt/nfs1/test
> root@vm:~/xfstests# ls -l /mnt/test/test
> -rw-r--r-- 1 root root 9223372036854775807 Feb  8 18:30 /mnt/test/test
> 
> so the file gets created with the correct size on the server, but
> the clients shows the size truncated.
> 
> This is extraced from xfstests generic/911 which tests clone
> functionality and fails because of this issue.

Took a quick look at wireshark, and GETATTR is returning the correct
(larger) size.

Also FSINFO (this is v3) returns 9223372036854775807 as the maximum file
size.

--b.

  reply	other threads:[~2016-02-08 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 18:33 silent truncation for large file offsets Christoph Hellwig
2016-02-08 19:30 ` J. Bruce Fields [this message]
2016-02-08 19:45   ` Trond Myklebust
2016-02-08 19:54     ` J. Bruce Fields
2016-02-08 20:04       ` Trond Myklebust
2016-02-08 19:58     ` Christoph Hellwig

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=20160208193012.GG17411@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@infradead.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.