From: Peter Staubach <staubach@redhat.com>
To: Kenny Simpson <theonetruekenny@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: An nfs question ftruncate vs. pwrite
Date: Wed, 07 Dec 2005 16:12:25 -0500 [thread overview]
Message-ID: <43975039.3080006@redhat.com> (raw)
In-Reply-To: <20051207203932.25422.qmail@web34103.mail.mud.yahoo.com>
Kenny Simpson wrote:
>When a file that is opened with normal flags (O_RDWR|O_CREAT|O_TRUNC|O_LARGEFILE) is on NFS, and
>it is exteded via ftruncate, the new expty pages get read back from the server before the system
>call returns:
> (from strace -T):
>ftruncate64(3, 41943040) = 0 <0.063866>
>
Is there a question in there?
If the question is whether the new empty pages get read in from the
server before the ftruncate system call returns, then no, they do not.
They get read in from the server as required in the normal course of
future operations.
Thanx...
ps
prev parent reply other threads:[~2005-12-07 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 20:39 An nfs question ftruncate vs. pwrite Kenny Simpson
2005-12-07 21:12 ` Peter Staubach [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=43975039.3080006@redhat.com \
--to=staubach@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=theonetruekenny@yahoo.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