From: Marek Behun <marek.behun@nic.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: when does btrfs create sparse extents?
Date: Wed, 22 Apr 2020 22:44:25 +0200 [thread overview]
Message-ID: <20200422224425.7f2c6459@nic.cz> (raw)
In-Reply-To: <CAJCQCtTDGb1hAAdp1-ph0wzFcfQNyAh-+hNMipdRmK0iTZA8Xw@mail.gmail.com>
On Wed, 22 Apr 2020 14:26:31 -0600
Chris Murphy <lists@colorremedies.com> wrote:
> But I wonder if other sources of this sparseness has been considered?
> Maybe the build system is creating or preserving sparseness? e.g. `tar
> --hole-detection` or `--sparse` is used.
I don't actually know how the kernel is copied into the /boot directory
in this case.
> Another possibility is Btrfs supports two kinds of holes in the
> on-disk format for sparse files. Maybe uboot only supported the
> original (current default) type, and the bug really fixed the newer
> 'no-holes' feature version?
No, U-Boot did not support holes at all.
next prev parent reply other threads:[~2020-04-22 20:44 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 [this message]
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
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=20200422224425.7f2c6459@nic.cz \
--to=marek.behun@nic.cz \
--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.