From: "valleysmail-lol5@yahoo.de" <valleysmail-lol5@yahoo.de>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: drawbacks of non-ECC RAM
Date: Fri, 17 Jan 2014 18:33:35 +0000 (GMT) [thread overview]
Message-ID: <1389983615.90027.YahooMailNeo@web172606.mail.ir2.yahoo.com> (raw)
I'd like to know if there are drawbacks in using btrfs with non-ECC RAM instead of using ext4 with non-ECC RAM. I know that some features of btrfs may rely on ECC RAM but is the chance of data corruption or even a damaged filesystem higher than when i use ext4 instead of btrfs?
I want to know this because i would like to use the snapshot feature of btrfs and ext4 does not support that. I will not use btrfs for fixing silent data corruption nor for using RAID like features or encryption. ZFS however checks files in the background (even if i don't want) and if it thinks there is an error it will fix it and i cannot disable this feature. So errors in RAM may corrupt my files or even more.
If you have some information regarding this topic or some good links i would be very happy! =)
next reply other threads:[~2014-01-17 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 18:33 valleysmail-lol5 [this message]
2014-01-17 20:40 ` drawbacks of non-ECC RAM Austin S Hemmelgarn
2014-01-17 23:18 ` Duncan
2014-01-18 0:52 ` Justus Seifert
2014-01-18 1:30 ` Fajar A. Nugraha
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=1389983615.90027.YahooMailNeo@web172606.mail.ir2.yahoo.com \
--to=valleysmail-lol5@yahoo.de \
--cc=linux-btrfs@vger.kernel.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