linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: A L <mail@lechevalier.se>
To: linux-btrfs@vger.kernel.org
Subject: Changes in 5.8.x cause compsize/bees failure
Date: Sat, 12 Sep 2020 19:13:21 +0200	[thread overview]
Message-ID: <632b888d-a3c3-b085-cdf5-f9bb61017d92@lechevalier.se> (raw)

I noticed that in (at least 5.8.6 and 5.8.8) there is some change in 
Btrfs kernel code that cause them to fail.

For example compsize now often/usually fails with: "Regular extent's 
header not 53 bytes (0) long?!?"

Bees is having plenty of errors too, and does not succeed to read any 
files (hash db is always empty). Perhaps this is an unrelated problem?



             reply	other threads:[~2020-09-12 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12 17:13 A L [this message]
2020-09-12 17:22 ` Changes in 5.8.x cause compsize/bees failure Oliver Freyermuth
2020-09-12 19:45   ` Filipe Manana
2020-09-12 20:36     ` A L
2020-09-12 20:43       ` Filipe Manana
2020-09-15  8:17 ` David Sterba
2020-09-15 18:34   ` Zygo Blaxell
2020-09-15 18:46     ` David Sterba
2020-09-15 18:48     ` Holger Hoffstätte

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=632b888d-a3c3-b085-cdf5-f9bb61017d92@lechevalier.se \
    --to=mail@lechevalier.se \
    --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;
as well as URLs for NNTP newsgroup(s).