Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Don Y <blockedofcourse@foo.invalid>
Newsgroups: sci.electronics.design
Subject: Re: DRAM accommodations
Date: Mon, 16 Sep 2024 19:31:35 -0700
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <vcapmb$3a145$2@dont-email.me>
References: <vbdcrs$gp01$1@dont-email.me> <vbflbe$tlhp$7@dont-email.me>
 <vcaiop$makp$1@paganini.bofh.team> <vcao57$3a145$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 17 Sep 2024 04:31:39 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="32ff6696ce38bb0c4624127f2057158e";
	logging-data="3474565"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/exCYFG6o/UJkEZBflIjHz"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Cancel-Lock: sha1:YakXaqNEk8g8cETRppMGR6Qb/6Q=
In-Reply-To: <vcao57$3a145$1@dont-email.me>
Content-Language: en-US
Bytes: 1708

On 9/16/2024 7:05 PM, Don Y wrote:
> OTOH, if the memory just sits there with the expectation that it
> will retain its intended contents without a chance to be corrected
> (by the ECC hardware), then bit-rot can continue increasing the
> possibility of a second bit failing while the first is still failed.

This is the fallacy of (disk) RAID; unless you do patrol reads
and actively scrub the media, you won't know about bit-rot
until it has had a chance to progress to a point where you
are vulnerable to it.

[That's why you scrub DRAM!]