linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Marek Behun <marek.behun@nic.cz>, linux-btrfs@vger.kernel.org
Subject: Re: when does btrfs create sparse extents?
Date: Thu, 23 Apr 2020 08:57:59 +0300	[thread overview]
Message-ID: <9f96fe0c-cbe5-12c8-67f5-2981c9273c5d@gmail.com> (raw)
In-Reply-To: <20200422205209.0e2efd53@nic.cz>

22.04.2020 21:52, Marek Behun пишет:
> Hello,
> 
> there was a bug fixed recently in U-Boot's btrfs driver - the driver
> failed to read files with sparse extents. This causes that sometimes
> device failes to boot Linux, since the kernel fails to load from
> storage.
> 

Do you mean that kernel image (vmlinuz?) had holes? Or there were some
other files that caused U-Boot to fail?

> So when does kernel's btrfs driver write sparse extents? Is it always
> when it finds a PAGE_SIZEd and aligned all-zeros block? Or is it more
> complicated?
> 
> Thanks.
> 
> Marek
> 


  parent reply	other threads:[~2020-04-23  5:58 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
2020-04-23 12:39               ` Filipe Manana
2020-04-23 19:50                 ` Chris Murphy
2020-04-23  5:57 ` Andrei Borzenkov [this message]
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=9f96fe0c-cbe5-12c8-67f5-2981c9273c5d@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marek.behun@nic.cz \
    /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;
as well as URLs for NNTP newsgroup(s).