From: Marek Behun <marek.behun@nic.cz>
To: Filipe Manana <fdmanana@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: when does btrfs create sparse extents?
Date: Thu, 23 Apr 2020 14:05:59 +0200 [thread overview]
Message-ID: <20200423140559.2762bb0c@nic.cz> (raw)
In-Reply-To: <CAL3q7H41C6do6SdBCfCmA==TT1nPJQ4dB0vTi_jsm0tYuvvsUA@mail.gmail.com>
On Thu, 23 Apr 2020 12:51:32 +0100
Filipe Manana <fdmanana@gmail.com> wrote:
> There's nothing in btrfs that converts a sequence of zeroes
> automatically to a hole.
>
> It always has to be done by user space, either by writes that leave
> holes intentionally (e.g. create file, write 64K to offset 0, write 4K
> to offset 128, leaves a hole from range 64K to 128K) or by hole
> punching through fallocate().
Thanks for this information. If you ever come to Prague, let me know,
we can have a beer :D
next prev parent reply other threads:[~2020-04-23 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 18:52 when does btrfs create sparse extents? Marek Behun
2020-04-22 20:26 ` Chris Murphy
2020-04-22 20:44 ` Marek Behun
2020-04-22 20:44 ` Chris Murphy
2020-04-22 20:58 ` Marek Behun
2020-04-22 21:05 ` Chris Murphy
2020-04-23 10:49 ` Filipe Manana
2020-04-23 11:42 ` Marek Behun
2020-04-23 11:51 ` Filipe Manana
2020-04-23 12:05 ` Marek Behun [this message]
2020-04-23 12:39 ` Filipe Manana
2020-04-23 19:50 ` Chris Murphy
2020-04-23 5:57 ` Andrei Borzenkov
2020-04-23 6:45 ` Marek Behun
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=20200423140559.2762bb0c@nic.cz \
--to=marek.behun@nic.cz \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.