From: Christoph Anton Mitterer <calestyo@scientia.org>
To: linux-btrfs@vger.kernel.org
Subject: call trace when btrfs-check tries to write on ro-blockdev
Date: Wed, 21 Sep 2022 04:29:37 +0200 [thread overview]
Message-ID: <70591e96d9dbc46cfaa44316f0eb1bcccc7017f5.camel@scientia.org> (raw)
Hey.
Not really a big problem but a but "ugly"...
When trying to do some write operation with btrfs check on a blockdev
that is set read-only, one gets a call trace like the following:
# btrfs check --clear-space-cache v1 /dev/mapper/data
Opening filesystem to check...
Checking filesystem on /dev/mapper/data-b-1
UUID: 18343f60-3955-11ed-a6c8-38afd7a81270
Error writing to device 1
kernel-shared/transaction.c:156: __commit_transaction: BUG_ON `ret`
triggered, value 1
btrfs(+0x3683b)[0x55c75780483b]
btrfs(__commit_transaction+0xc6)[0x55c757804b32]
btrfs(btrfs_commit_transaction+0x130)[0x55c757804ca0]
btrfs(+0x61963)[0x55c75782f963]
btrfs(+0x6e297)[0x55c75783c297]
btrfs(main+0x318)[0x55c7577e6138]
/lib/x86_64-linux-gnu/libc.so.6(+0x2920a)[0x7f6fd6ff920a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x7c)[0x7f6fd6ff92bc]
btrfs(_start+0x21)[0x55c7577e6171]
Aborted
Cheers,
Chris.
PS: That was with progs 5.19.
next reply other threads:[~2022-09-21 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 2:29 Christoph Anton Mitterer [this message]
2022-09-21 2:40 ` call trace when btrfs-check tries to write on ro-blockdev Qu Wenruo
2022-09-21 3:43 ` Christoph Anton Mitterer
2022-09-23 10:39 ` Qu Wenruo
2022-09-23 18:53 ` 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:
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=70591e96d9dbc46cfaa44316f0eb1bcccc7017f5.camel@scientia.org \
--to=calestyo@scientia.org \
--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).