From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: delayed_refs has NO entry / btrfs_update_root:136: Aborting unused transaction(No space left).
Date: Wed, 20 Mar 2019 01:59:26 +0100 [thread overview]
Message-ID: <d35fa8de087c746f9affb789cf3ab599a3d042c1.camel@scientia.net> (raw)
In-Reply-To: <b2a668d7124f1d3e410367f587926f622b3f03a4.camel@scientia.net>
Anything I should do with respect to this?
I.e. is further debug info needed for an interested developer? or can I
simply scrap that particular image (which is not an important one)?
Cheers,
Chris.
On Sun, 2019-03-17 at 04:42 +0100, Christoph Anton Mitterer wrote:
> (resending,... seems this hasn't gotten through to the list, when
> I've
> sent it the first time)
>
>
> Hi.
>
> On Debian's 4.19.28-2 kernel (which includes the recent read-
> corruption
> on compression fix) the following happens:
>
> As a consequence of the bug from the "Reproducer for "compressed data
> +
> hole data corruption bug, 2018 edition" still works on 4.20.7" mail
> thread I started (trying) to verify whether any of my data was
> affected.
>
> Part of this was looking for files which actually are compressed by
> the
> two methods Zygo mentioned (compsize and filefrag -v).
>
> For this I used two scripts like the attached ones (yes I know, bad
> performance) being fed by find path -type f -exec script {} \; .
>
>
> I've did this already on one of my disks, which I btrfs checked
> before
> (both normal and lowmem mode with no error), blockdev --setro'ed the
> device and mounted it ro.
>
> The filefrag seems to cause all kinds of errors and call traces,
> giving
> the dmesg output attached.
>
>
> Any ideas what causes that?
>
>
> These days I unfortunately strongly loose trust in the stability and
> integrity of btrfs :-(
>
>
> Cheers,
> Chris.
next prev parent reply other threads:[~2019-03-20 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 3:42 delayed_refs has NO entry / btrfs_update_root:136: Aborting unused transaction(No space left) Christoph Anton Mitterer
2019-03-20 0:59 ` Christoph Anton Mitterer [this message]
2019-03-20 9:59 ` Johannes Thumshirn
2019-04-12 22:46 ` Christoph Anton Mitterer
2019-04-12 22:52 ` Christoph Anton Mitterer
2019-04-15 8:42 ` Johannes Thumshirn
2019-05-03 2:42 ` Christoph Anton Mitterer
2019-05-16 9:12 ` Christoph Anton Mitterer
2019-05-29 13:55 ` Patch "Btrfs: do not start a transaction during fiemap" Christoph Anton Mitterer
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=d35fa8de087c746f9affb789cf3ab599a3d042c1.camel@scientia.net \
--to=calestyo@scientia.net \
--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).