Linux-BTRFS Archive on
 help / color / Atom feed
From: Christoph Anton Mitterer <>
To: linux-btrfs <>
Subject: delayed_refs has NO entry / btrfs_update_root:136: Aborting unused transaction(No space left).
Date: Sun, 17 Mar 2019 04:42:39 +0100
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

(resending,... seems this hasn't gotten through to the list, when I've
sent it the first time)


On Debian's 4.19.28-2 kernel (which includes the recent read-
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

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 :-(


[-- Attachment #2: compsize-compressed --]
[-- Type: application/x-shellscript, Size: 225 bytes --]

[-- Attachment #3: filefrag-compressed --]
[-- Type: application/x-shellscript, Size: 217 bytes --]

[-- Attachment #4: dmesg.xz --]
[-- Type: application/x-xz, Size: 5424 bytes --]

             reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17  3:42 Christoph Anton Mitterer [this message]
2019-03-20  0:59 ` Christoph Anton Mitterer
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-BTRFS Archive on

Archives are clonable:
	git clone --mirror linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ \
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone