From: Bakul Shah <bakul@iitbombay.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] VFS prior to 1984
Date: Mon, 6 Jul 2020 18:07:34 -0700 [thread overview]
Message-ID: <C9BE297A-CBDD-4781-9DA1-93B79C5595FA@iitbombay.org> (raw)
In-Reply-To: <202007061651.066GpW9s048139@elf.torek.net>
On Jul 6, 2020, at 9:51 AM, Chris Torek <torek@torek.net> wrote:
>
>> On Sun, Jul 05, 2020 at 10:05:57AM +1000, Dave Horsfall wrote:
>> We found a bunch of those because computers used to be ECC or parity and
>> then 15 years ago or so, they just dumped the parity bit so single bit
>> errors go unreported (noice, computer industry).
>
> To be fair, there are still some ECC systems. Unfortunately most
> of the home-use Intel boxes aren't. My own home-use box isn't and
> (now 6+ years ago) I had bad RAM in it that produced single-bit
> errors in an inode block that led to panics that led to me finding
> the single-bit errors, but I don't know if there are some damaged
> files.
>
> I keep thinking I'll replace it with a new box that does have ECC,
> but haven't gotten around to it yet. I see some consumer-priced
> AMD CPUs have at least theoretical ECC support but I haven't found
> anything that says the ECC actually works, and have seen a few
> articles that hint that it doesn't. iX sells NAS boxes that do
> have ECC, though.
For my fileserver I am using a Gigabyte X470 Aorus Gaming board
with "qualified" ECC RAM (dmidecode confirms this) but I am not
sure if FreeBSD has ECC support for such boards. At least I don't
know how to tell!
What I really want is a laptop with ECC to use as the fileserver
to avoid having to deal with UPS that lasts a few minutes, cabling
and suboptimal support from NUT. SSDs are fast enough for me.
Laptop batteries last long and are easy to replace and easy to
test when to shutdown the laptop. And less heat and space!
next prev parent reply other threads:[~2020-07-07 1:08 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 9:09 Paul Ruizendaal
2020-06-23 14:01 ` Larry McVoy
2020-06-23 15:12 ` Clem Cole
2020-06-23 15:55 ` Rich Morin
2020-06-23 20:38 ` Rob Pike
2020-06-23 20:57 ` Larry McVoy
2020-06-24 5:14 ` arnold
2020-06-24 21:08 ` Dave Horsfall
2020-06-24 19:30 ` Clem Cole
2020-06-24 19:36 ` Larry McVoy
2020-06-25 6:52 ` Rob Gingell
2020-07-05 0:05 ` Dave Horsfall
2020-07-05 0:16 ` Larry McVoy
2020-07-06 4:42 ` Dave Horsfall
2020-07-06 16:51 ` Chris Torek
2020-07-06 23:23 ` [TUHS] ECC memory John Gilmore
2020-07-07 1:07 ` Bakul Shah [this message]
2020-07-05 1:43 ` [TUHS] VFS prior to 1984 Clem Cole
2020-07-05 14:43 ` Larry McVoy
2020-07-05 18:40 ` Arthur Krewat
2020-07-05 20:08 ` Clem Cole
2020-07-05 20:42 ` John Cowan
2020-07-05 21:04 ` Clem Cole
2020-07-05 21:14 ` Dan Cross
2020-06-24 16:51 ` Anthony Martin
2020-06-24 17:31 ` Anthony Martin
2020-06-24 18:31 ` Paul Ruizendaal
2020-06-25 0:56 ` Rob Gingell via TUHS
2020-06-25 4:15 ` [TUHS] Oh, things were very different Rich Morin
2020-06-25 15:45 ` Lawrence Stewart
2020-06-25 16:24 ` Warner Losh
2020-06-25 17:57 ` Arthur Krewat
2020-06-25 20:22 ` Dave Horsfall
2020-06-25 20:42 ` Michael Kjörling
2020-06-25 20:49 ` Clem Cole
2020-06-26 0:48 ` Dave Horsfall
2020-06-24 19:05 ` [TUHS] VFS prior to 1984 Paul Ruizendaal
2020-06-24 20:27 ` Derek Fawcus
2020-06-24 21:33 ` Greg A. Woods
2020-06-25 0:45 ` Adam Thornton
2020-06-25 19:40 ` Greg A. Woods
2020-06-23 22:17 Norman Wilson
2020-06-23 22:24 ` Dave Horsfall
2020-06-24 4:09 ` Warner Losh
2020-06-24 5:10 ` Dave Horsfall
2020-06-24 5:33 ` Bakul Shah
2020-06-24 9:10 ` Andrew Warkentin
2020-06-24 14:31 Noel Chiappa
2020-06-24 15:21 ` Clem Cole
2020-06-24 17:51 Noel Chiappa
2020-06-24 18:13 ` Richard Salz
2020-06-24 18:46 ` Lars Brinkhoff
2020-06-24 18:31 Norman Wilson
2020-06-25 6:22 ` arnold
2020-06-25 19:31 Noel Chiappa
2020-06-25 20:23 Noel Chiappa
2020-06-25 20:25 Noel Chiappa
2020-06-26 5:49 ` Lars Brinkhoff
2020-06-26 8:34 ` Dave Horsfall
2020-06-26 11:13 ` arnold
2020-06-29 9:11 Paul Ruizendaal
2020-06-29 14:45 ` Larry McVoy
2020-06-29 14:53 ` Paul Ruizendaal
2020-06-29 15:14 ` Larry McVoy
2020-06-29 16:34 ` Heinz Lycklama
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=C9BE297A-CBDD-4781-9DA1-93B79C5595FA@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).