From: Nathan Scott <nscott@aconex.com>
To: Bhagi rathi <jahnu77@gmail.com>, David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: TAKE 972756 - Implement fallocate.
Date: Wed, 07 Nov 2007 09:38:53 +1100 [thread overview]
Message-ID: <1194388733.3862.206.camel@edge.yarra.acx> (raw)
In-Reply-To: <20071106204100.GW995458@sgi.com>
On Wed, 2007-11-07 at 07:41 +1100, David Chinner wrote:
> > Preallocation happened from 1k to 256k. Now, it looks to me that we
> have
> > un-written extents from 4k to 256k. There is no guarantee that data
> from 1k
> > to 4k is all zero'es.
That guarantee does exist - when the initial 1K block write is done, the
end of the block is zeroed (by the kernel write path). This is always
done (guaranteed) and is required independently to unwritten extents.
cheers.
--
Nathan
next prev parent reply other threads:[~2007-11-06 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 2:43 TAKE 972756 - Implement fallocate David Chinner
2007-11-05 18:42 ` Bhagi rathi
2007-11-06 0:12 ` David Chinner
2007-11-06 17:27 ` Bhagi rathi
2007-11-06 19:04 ` Eric Sandeen
2007-11-06 20:41 ` David Chinner
2007-11-06 22:38 ` Nathan Scott [this message]
2007-11-07 5:42 ` Bhagi rathi
2007-11-07 9:35 ` nscott
2007-12-10 17:50 ` Eric Sandeen
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=1194388733.3862.206.camel@edge.yarra.acx \
--to=nscott@aconex.com \
--cc=dgc@sgi.com \
--cc=jahnu77@gmail.com \
--cc=xfs@oss.sgi.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