I cannot help but feel it would be quite awesome if ZFS-fuse were a part of this:
--
--
To post to this group, send email to zfs-...@googlegroups.com
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
That sounds like a lot of handwaving and hearsay. The point remains that ZFS' design still makes it more resistant to issues like this than a traditional file system. I'm happy to be persuaded otherwise, but I'd need to see a specific case in which a single bit flip will destroy a ZFS pool and conclusive proof that a single bit flip _cannot_ similarly destroy a data set on a more traditional storage stack.
If the aim was to show that ZFS can be more risky than a traditional FS, this falls well short. Especially since I can demonstrate that ZFS has protected my data from damage due to silent disk corruption a large number of times already.
Gordan
On 09/20/2013 07:41 PM, Emmanuel Anne wrote:
http://hardware.slashdot.org/comments.pl?sid=4226771&cid=44881099
This should point directly to the right comment !
2013/9/20 Durval Menezes <durval....@gmail.com
<mailto:durval.menezes@gmail.com>>
<mailto:zfs-fuse@googlegroups.com>
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed
to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving
emails from it, send an email to
<mailto:zfs-fuse%2Bunsu...@googlegroups.com>.
For more options, visit
https://groups.google.com/groups/opt_out.
--
--
To post to this group, send email to
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to
the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
<mailto:zfs-fuse%2Bunsu...@googlegroups.com>.
For more options, visit
https://groups.google.com/groups/opt_out.
--
my zfs-fuse git repository :
http://rainemu.swishparty.co.uk/cgi-bin/gitweb.cgi?p=zfs;a=summary
--
--
To post to this group, send email to
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the
Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
<mailto:zfs-fuse%2Bunsu...@googlegroups.com>.
For more options, visit
https://groups.google.com/groups/opt_out.
--
--
To post to this group, send email to zfs-...@googlegroups.com
<mailto:zfs-fuse@googlegroups.com>
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the
Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to zfs-fuse+unsubscribe@googlegroups.com
<mailto:zfs-fuse%2Bunsu...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
To post to this group, send email to zfs-...@googlegroups.com
<mailto:zfs-fuse@googlegroups.com>
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google
Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to zfs-fuse+unsubscribe@googlegroups.com<mailto:zfs-fuse%2Bunsu...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
--
my zfs-fuse git repository :
http://rainemu.swishparty.co.uk/cgi-bin/gitweb.cgi?p=zfs;a=summary
--
--
To post to this group, send email to zfs-...@googlegroups.com
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google
Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to zfs-fuse+unsubscribe@googlegroups.com.
To visit our Web site, click on http://zfs-fuse.net/
--- You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+unsubscribe@googlegroups.com.
--
--
To post to this group, send email to zfs-...@googlegroups.com
To visit our Web site, click on http://zfs-fuse.net/
--- You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Yes, in order to get the resilience that ZFS offers you must have some form of redundancy in your pool. Mirrors or raidz, extra copies, and backups; take as many as you can. One bit-flip every few years is pretty average; it depends on how much data you read from the drive. As disk capacities go up and file sizes increase it get more and more likely.
I wonder though if you could use zdb to get at the contents of the stripe that suffered the bit-flip. Maybe that would let you restore the file.
db48x
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+u...@googlegroups.com.
Well all I can say is that it never happened to me since I use hard disks, and so it's quite a long time already (1st hard disk must have been on the atari st, so it was before 1990 !). Of course maybe it happened but I never noticed it anyway, but the fact is that I never noticed any problem of this kind so far.
With zfs it happened within 3 years, which is quite a short time, and where a single bit flip could have almost no consequences on some types of files, here it makes a whole 128k block totally unreadable, which actually makes the file corrupt.Anyway just remember to use mirroring and/or ecc ram and everything should be fine, just avoid a single pool without ecc ram, that's all !