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@xxxxxxx +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
