Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Sunday July 16 2017, @11:42PM   Printer-friendly
from the it's-all-ones-and-zeroes dept.

Stephen Foskett has written a detailed post about why he considers ZFS the Best Filesystem (For Now...). He starts out:

ZFS should have been great, but I kind of hate it: ZFS seems to be trapped in the past, before it was sidelined it as the cool storage project of choice; it's inflexible; it lacks modern flash integration; and it's not directly supported by most operating systems. But I put all my valuable data on ZFS because it simply offers the best level of data protection in a small office/home office (SOHO) environment. Here's why.

It's been a long road to get to where it is and there have been many hinderances, including software patents and malicious licensing.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Monday July 17 2017, @05:21PM

    by Anonymous Coward on Monday July 17 2017, @05:21PM (#540410)

    I agree that ECC RAM *should* be on a server, or a device that does a lot of services intended for be accessed by clients.

    It used to be all of my computers had parity memory -- then non-parity came out and it wasn't just cheaper... but the parity ram costs went up while the new ram costs were less that the original parity ram.

    Now, it is very hard to get high speed, high density, ecc ram at a price that is reasonable. Reasonable is in the eye of the purchaser and system operator I guess, but often it's not cheap and it is not often one can point at an issue and say "yes this would have been prevented if you had ECC ram".

    Instead, errors are found in existing ram when the system crashes, if they are found proactively at all. Few people take their production systems down to run memtest 86 just to do it.

    Silent corruption of data often has a few potential causes, with memory only being one of them.

    A good approach is to do read only caching on non-ecc file systems... (or get lead foil shielding for those that use deferred writes!)