Hacker News new | ask | show | jobs
by SkyMarshal 1822 days ago
Also a good idea to use ECC Memory with the ZFS filesystem. That combination can correct any single-bit error, and detect and warn about any double-bit error, significantly reducing the chance of losing data to bitrot.

And if you’re backing up your keys on USB drives, use high-endurance SLC NAND industrial drives. They provide the highest reliability and endurance available.

https://www.embeddedarm.com/blog/slc-nand-secrets-exposed/

1 comments

"There's nothing special about ZFS that requires/encourages the use of ECC RAM more so than any other filesystem."-Matthew Ahrens
His full quote, from the actual source (2003):

"There's nothing special about ZFS that requires/encourages the use of ECC RAM more so than any other filesystem. If you use UFS, EXT, NTFS, btrfs, etc without ECC RAM, you are just as much at risk as if you used ZFS without ECC RAM. Actually, ZFS can mitigate this risk to some degree if you enable the unsupported ZFS_DEBUG_MODIFY flag (zfs_flags=0x10). This will checksum the data while at rest in memory, and verify it before writing to disk, thus reducing the window of vulnerability from a memory error.

I would simply say: if you love your data, use ECC RAM. Additionally, use a filesystem that checksums your data, such as ZFS."

https://arstechnica.com/civis/viewtopic.php?f=2&t=1235679&p=...

Exactly. You are at no greater risk of data loss if you use ZFS as appose to another file system.

You stated "Also a good idea to use ECC Memory with the ZFS filesystem".

You should have probably stated its a good idea to use ECC memory, period. Instead you tied ECC to ZFS.

I would simply say: if you love your data, use ECC RAM. Additionally, use a filesystem that checksums your data, such as ZFS.

Both are better than either, and either is better than neither. Especially if you're storing cryptocurrencies on it.