From: Roman Mamedov <rm@romanrm.net>
To: Marc MERLIN <marc@merlins.org>
Cc: Qu Wenruo <wqu@suse.com>, 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>,
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 14:25:05 +0500 [thread overview]
Message-ID: <20250225142505.276af40f@nvm> (raw)
In-Reply-To: <Z72LAZDq8IegQoua@merlins.org>
On Tue, 25 Feb 2025 01:18:57 -0800
Marc MERLIN <marc@merlins.org> wrote:
> 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?
There is memtester: https://pyropus.ca./software/memtester/
But it can't test 100% of the RAM, only the free userspace area that it can
allocate. You should close down most apps and then give it (as a parameter) as
high amount as possible, without it getting killed by OOM. It could catch very
obvious faults, and it is a good "something to do" for now :) but for the
complete rigorous test you'll need the baremetal memtest86+.
--
With respect,
Roman
next prev parent reply other threads:[~2025-02-25 9:31 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
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 [this message]
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=20250225142505.276af40f@nvm \
--to=rm@romanrm.net \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=marc@merlins.org \
--cc=quwenruo.btrfs@gmx.com \
--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