From: Filipe Manana <fdmanana@gmail.com>
To: Oliver Freyermuth <o.freyermuth@googlemail.com>
Cc: A L <mail@lechevalier.se>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Changes in 5.8.x cause compsize/bees failure
Date: Sat, 12 Sep 2020 20:45:33 +0100 [thread overview]
Message-ID: <CAL3q7H4s1W33DovgTJRAr3qTh+wjPZqbiHUjmvPMqQ=rce8YMQ@mail.gmail.com> (raw)
In-Reply-To: <dccf4603-ee16-37e0-11b2-d72f8956a74b@googlemail.com>
On Sat, Sep 12, 2020 at 6:27 PM Oliver Freyermuth
<o.freyermuth@googlemail.com> wrote:
>
> Am 12.09.20 um 19:13 schrieb A L:
> > 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?!?"
>
> I noticed the same after upgrade from 5.8.5 to 5.8.8 and reported it to compsize:
> https://github.com/kilobyte/compsize/issues/34
> However, since it's userspace breakage, indeed it's probably a good idea to also report here.
>
> Since you see it with 5.8.6 already and I did not observe it in 5.8.5, this should pin it down to the 5.8.6 patchset.
> Sadly, I don't have time at hand for a bisect at the moment, and at first glance, none of the commits strikes me in regard to this issue (I don't use qgroups on my end).
>
> >
> > 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?
> >
Can any of you try the following patch and see if it fixes the issue?
https://pastebin.com/vTdxznbh
Thanks.
> >
--
Filipe David Manana,
“Whether you think you can, or you think you can't — you're right.”
next prev parent reply other threads:[~2020-09-12 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 17:13 Changes in 5.8.x cause compsize/bees failure A L
2020-09-12 17:22 ` Oliver Freyermuth
2020-09-12 19:45 ` Filipe Manana [this message]
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='CAL3q7H4s1W33DovgTJRAr3qTh+wjPZqbiHUjmvPMqQ=rce8YMQ@mail.gmail.com' \
--to=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mail@lechevalier.se \
--cc=o.freyermuth@googlemail.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 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).