From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: 5.16.0-0.rc5, btrfs-transacti:9822 blocked, write time tree block corruption, parent transid verify failed, error in free_log_tree, forced ro
Date: Mon, 13 Dec 2021 22:14:57 -0500 [thread overview]
Message-ID: <CAJCQCtT4VLkjLqwNUKJMTvYPH6rsQomDX7UAb0iYoWv-M8iOCw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtT+RSzpUjbMq+UfzNUMe1X5+1G+DnAGbHC=OZ=iRS24jg@mail.gmail.com>
I can't tell for sure which Btrfs file system is the instigator. But
looks to me like it stalled pretty soon after I mounted this
/dev/loop0 Btrfs. The stack is:
NVMe->plain partition->Btrfs->nodatacow file->LUKS/dmcrypt->Btrfs
Dec 13 21:39:42 kernel: loop0: detected capacity change from 0 to 2097152
Dec 13 21:39:42 kernel: BTRFS: device fsid
a1510170-f603-4015-b7f0-2731c85504a6 devid 1 transid 91448 /dev/dm-0
scanned by systemd-udevd (9795)
Dec 13 21:39:44 kernel: BTRFS info (device dm-0): use zstd compression, level 1
Dec 13 21:39:44 kernel: BTRFS info (device dm-0): using free space tree
Dec 13 21:39:44 kernel: BTRFS info (device dm-0): has skinny extents
Dec 13 21:39:44 kernel: BTRFS info (device dm-0): enabling ssd optimizations
...
Dec 13 21:42:47 kernel: INFO: task btrfs-transacti:9822 blocked for
more than 122 seconds.
Dec 13 21:42:47 kernel: Tainted: G W --------- ---
5.16.0-0.rc5.35.fc36.x86_64+debug #1
--
Chris Murphy
next prev parent reply other threads:[~2021-12-14 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 2:58 5.16.0-0.rc5, btrfs-transacti:9822 blocked, write time tree block corruption, parent transid verify failed, error in free_log_tree, forced ro Chris Murphy
2021-12-14 3:14 ` Chris Murphy [this message]
2021-12-14 11:37 ` Filipe Manana
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=CAJCQCtT4VLkjLqwNUKJMTvYPH6rsQomDX7UAb0iYoWv-M8iOCw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=josef@toxicpanda.com \
--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).