From: Roland Dreier <rdreier@cisco.com>
To: Paul Komkoff <i@stingr.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs fallocate woes
Date: Thu, 14 Jan 2010 09:27:38 -0800 [thread overview]
Message-ID: <aday6k0lhpx.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <715ea5c11001140328g6198447axce1ba884a6e6fb96@mail.gmail.com> (Paul Komkoff's message of "Thu, 14 Jan 2010 11:28:39 +0000")
> if you run it on ext4, it will create a 4-byte file with "test" in it.
> On btrfs, however, the file size would be 4096, and the remaining
> space will be filled with zeroes.
My fallocate man page says:
Because allocation is done in block size chunks, fallocate() may
allocate a larger range than that which was specified.
so the btrfs behavior seems OK to me.
You say this is a regression. What btrfs version behaved differently?
- R.
next prev parent reply other threads:[~2010-01-14 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 11:28 btrfs fallocate woes Paul Komkoff
2010-01-14 17:27 ` Roland Dreier [this message]
2010-01-14 18:24 ` Paul Komkoff
2010-01-14 18:25 ` Paul Komkoff
2010-01-14 18:26 ` Aneesh Kumar K. V
2010-01-14 19:20 ` Chris Mason
2010-01-14 20:33 ` Paul Komkoff
2010-01-19 15:18 ` Paul Komkoff
2010-01-20 7:28 ` Aneesh Kumar K. V
2010-01-20 15:13 ` Paul Komkoff
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=aday6k0lhpx.fsf@roland-alpha.cisco.com \
--to=rdreier@cisco.com \
--cc=i@stingr.net \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox