As someone who has spent easily 100 hours troubleshooting, rebuilding, and restoring UFS based Netgate boxes that have to function in environments with less-that-datacenter grade power availability, I'll take "potential corruption in corner cases" over "1 in 4 chance it won't come back from a power cycle"

*Any* journaled filesystem is an improvement.

On 3/8/18 06:19, Vick Khera wrote:
On Wed, Mar 7, 2018 at 8:18 PM, Walter Parker <> wrote:

don't use ECC. Can anyone show why my solution should switch file systems
(given that I'm keeping my existing hardware) without changing the subject?
I've read many of the scare stories from FreeNAS and they all seem to end
up as a call to authority or a "fine, risk your data" without actually
answering the question.

The most important feature I use in ZFS is the snapshots. Combined cleverly
with datasets and quotas, they make for very easy management of disk
resources when needed. The FreeNAS model of boot environments is awesome,
and I hope pfSense takes those up as well. It makes upgrades less stressful
when you can just click a button to revert.

As for the ECC, see this study
for example. It is slightly old, but RAM hardware is not that much advanced
since then. Basically, if you have a few gigs of RAM in your machine, it
*will* produce bit errors.  There are other studies that back this up too,
and they are more recent.

Personally, I don't understand why any computer, desktop or server, made
these days is without ECC. My desktop has 16GB RAM with room for 16 more.
I'm sure there are flipped bits in some of my work somewhere, but I'll
never really know. If I'm lucky, the flipped bits are on unused sections of
code loaded from the disk into RAM.
pfSense mailing list
Support the project with Gold!

pfSense mailing list
Support the project with Gold!

Reply via email to