Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
* delayed_refs has NO entry / btrfs_update_root:136: Aborting unused transaction(No space left).
@ 2019-03-17  3:42 Christoph Anton Mitterer
  2019-03-20  0:59 ` Christoph Anton Mitterer
                   ` (2 more replies)
  0 siblings, 3 replies; 9+ messages in thread
From: Christoph Anton Mitterer @ 2019-03-17  3:42 UTC (permalink / raw)
  To: linux-btrfs

[-- 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)


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.

[-- 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 --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, back to index

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 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/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git