From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS error (device dm-4): failed to run delayed ref for logical 350223581184 num_bytes 16384 type 176 action 1 ref_mod 1: -117 (kernel 6.11.2)
Date: Thu, 6 Feb 2025 09:34:29 -0800 [thread overview]
Message-ID: <Z6TypSioRGfQi1C7@merlins.org> (raw)
In-Reply-To: <Z6TsUwR7tyKJrZ7w@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Thu, Feb 06, 2025 at 09:07:31AM -0800, Marc MERLIN wrote:
> [1821331.237716] item 0 key (350222417920 169 0) itemoff 16250 itemsize 33
> [1821331.237718] extent refs 1 gen 2907391 flags 2
> [1821331.237719] ref#0: tree block backref root 398
> (...(
> [1821331.238559] item 167 key (350225678336 169 0) itemoff 7733 itemsize 168
> [1821331.238560] extent refs 16 gen 4619087 flags 2
> [1821331.238561] ref#0: tree block backref root 398
> [1821331.238562] ref#1: shared block backref parent 737084112896
> [1821331.238563] ref#2: shared block backref parent 736609173504
> [1821331.238564] ref#3: shared block backref parent 471099588608
> [1821331.238565] ref#4: shared block backref parent 471017488384
> [1821331.238567] ref#5: shared block backref parent 470665625600
> [1821331.238568] ref#6: shared block backref parent 350806835200
> [1821331.238569] ref#7: shared block backref parent 350292066304
Sorry, I forgot to include the bzip'ed keys (big output, felt like too
much to paste, but maybe it's important)
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
[-- Attachment #2: keys.bz2 --]
[-- Type: application/octet-stream, Size: 6394 bytes --]
next prev parent reply other threads:[~2025-02-06 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 17:07 BTRFS error (device dm-4): failed to run delayed ref for logical 350223581184 num_bytes 16384 type 176 action 1 ref_mod 1: -117 (kernel 6.11.2) Marc MERLIN
2025-02-06 17:34 ` Marc MERLIN [this message]
2025-02-25 7:32 ` Marc MERLIN
2025-02-25 8:07 ` Qu Wenruo
2025-02-25 8:29 ` Marc MERLIN
2025-02-25 8:46 ` Qu Wenruo
2025-02-25 9:18 ` Marc MERLIN
2025-02-25 9:22 ` Qu Wenruo
2025-02-27 14:11 ` Marc MERLIN
2025-02-27 15:05 ` Marc MERLIN
2025-02-28 13:10 ` Marc MERLIN
2025-02-25 9:25 ` Roman Mamedov
2025-02-27 17:02 ` Boris Burkov
2025-02-27 17:21 ` Boris Burkov
2025-02-27 17:33 ` Marc MERLIN
2025-02-27 17:41 ` Filipe Manana
2025-02-27 19:57 ` Marc MERLIN
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=Z6TypSioRGfQi1C7@merlins.org \
--to=marc@merlins.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