Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
	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 10:59:51 +0100
Message-ID: <9ff84820-5d7e-f541-6adc-29c4949d44e0@suse.de> (raw)
In-Reply-To: <d35fa8de087c746f9affb789cf3ab599a3d042c1.camel@scientia.net>

On 20/03/2019 01:59, Christoph Anton Mitterer wrote:
> 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)?


OK, I can give it a shot, but please be aware I'm still relatively new
to BTRFS.

First of all, have you tried a more recent kernel than the Debian
kernels you referenced? E.g. Linus' current master or David's misc-next
branch? Just so we don't try to hunt down a bug that's already fixed.

If it's still reproducible with a more recent kernel, I think having an
image would be very valuable.

From the dmesg (I don't have the referenced kernel version handy, Greg's
4.19.27 is the closest I have) we're hitting this WARN_ON():

        WARN_ON(cur_trans != info->running_transaction);

Which means there's a mismatch between the transaction that's currently
running and the transaction the filesystem thinks is running, if I read
it correctly.

Also if you can still reproduce the bug, please activate tracing in
btrfs and send the trace output.

Byte,
	Johannes
-- 
Johannes Thumshirn                            SUSE Labs Filesystems
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17  3:42 Christoph Anton Mitterer
2019-03-20  0:59 ` Christoph Anton Mitterer
2019-03-20  9:59   ` Johannes Thumshirn [this message]
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 publically 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=9ff84820-5d7e-f541-6adc-29c4949d44e0@suse.de \
    --to=jthumshirn@suse.de \
    --cc=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

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