Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: BP25 <bp25@posteo.net>
To: linux-btrfs@vger.kernel.org
Subject: How to detect ram memory going bad?
Date: Wed, 19 Nov 2025 14:31:53 +0000	[thread overview]
Message-ID: <665d612165e1f21e681d3b1229bcd40f@posteo.net> (raw)

Hello I'm writing to this mailing list as suggested by the btrfs docs. I 
wanted to ask how to detect and mitigate ram memory going bad when using 
BTRFS? Because the 'Hardware Considerations' the BTRFS manual suggest in 
this scenario to run memtest; but this is probs more like right after 
installing new ram. Is there any BTRFS tool, perhaps to run 
periodically, that can help me detect bad ram hence mitigate the 
consequences? There is a webpage called 'Will ZFS and non-ECC RAM kill 
your data?' where it's suggested that ZFS scrub effectively detects bad 
ram (when at least two copies of the same file and/or metadata are 
stored, and I wonder if there are other assumptions here...), but I'm 
new to btrfs and I wonder if the reasoning can be applied to btrfs as 
well, and how effective of a mitigation it would actually provide. OS is 
GNU (Guix) and I think can't use ECC because I suspect my X200 
motherboards wouldn't support it?

Please CC: or BCC: me cause I'm not subscribed.

             reply	other threads:[~2025-11-19 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 14:31 BP25 [this message]
2025-11-19 20:54 ` How to detect ram memory going bad? Qu Wenruo

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=665d612165e1f21e681d3b1229bcd40f@posteo.net \
    --to=bp25@posteo.net \
    --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