From: Marc MERLIN <marc@merlins.org>
To: Qu Wenruo <wqu@suse.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Chris Murphy <lists@colorremedies.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
Roman Mamedov <rm@romanrm.net>, Su Yue <suy.fnst@cn.fujitsu.com>
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: Tue, 25 Feb 2025 01:18:57 -0800 [thread overview]
Message-ID: <Z72LAZDq8IegQoua@merlins.org> (raw)
In-Reply-To: <d973b4b7-0d98-4310-bb7e-50f87c374762@suse.com>
On Tue, Feb 25, 2025 at 07:16:31PM +1030, Qu Wenruo wrote:
> Ref#13 is the root that mentioned has the existing one.
>
> I have no idea why it shows up like this.
>
> But since the fs passes btrfs check, mind to dump the following tree block?
>
> # btrfs ins dump-tree -t extent <device> | grep "(350223581184 " -A 50
>
> I want to make sure if the ref 398 exists on disk, or it's generated at
> runtime.
sauron:~# btrfs ins dump-tree -t extent /dev/mapper/pool1 | grep "350223581184 " -A 50
sauron:~#
Mmmmh, so 350223581184 is gone now since it's been 20 days already since
my original post.
I can try to re-enable balance and see if things crash or not.
> I believe your machine is a ThinkPad P17 gen2 with a mobile Xeon, with DDR4
> ECC memory support, but I'm not sure if your memory sticks have ECC.
model name : Intel(R) Xeon(R) W-11855M CPU @ 3.20GHz
sauron:~# dmesg | grep -i EDAC
[ 1.293722] EDAC MC: Ver: 3.0.0
sauron:~# dmidecode -t memory | grep Width
Total Width: 64 bits
Data Width: 64 bits
Total Width: 64 bits
Data Width: 64 bits
Total Width: 64 bits
Data Width: 64 bits
Total Width: 64 bits
Data Width: 64 bits
That seems do say I do not have ECC or width would be 72 from what I
read :-/
> Just as a precaution, please run a memtest (I know it will be painfully
> slow, so please only run it after the above dump is taken).
I do not have the system with me right now and I think memtest cannot be
run from inside linux, correct?
If so, I can do this when I get home and can reboot the system.
Or is there a version I can run from inside linux?
Marc
--
"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
next prev parent reply other threads:[~2025-02-25 9:19 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
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 [this message]
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=Z72LAZDq8IegQoua@merlins.org \
--to=marc@merlins.org \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=rm@romanrm.net \
--cc=suy.fnst@cn.fujitsu.com \
--cc=wqu@suse.com \
/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