trionic
Explorer
- Joined
- May 1, 2014
- Messages
- 98
ZFS seems to have two modes: "everything's fine" (within the limits of redundancy) and "your pool's gone" (PS: "there are no recovery tools").
All is well until suddenly it's not and all your data's gone. With ZFS the risk of a catastrophic failure are low but the consequences are devastating.
Right now, on the verge of my first ZFS build, I am not comfortable with that consequence. I know, mirrors, backups etc, but some of the reasons for pool loss seem more and more to me like design flaws. For example: loss of a VDEV = pool loss; corrupted system metadata = pool loss. ZFS does not degrade gracefully.
The purpose of this thread is not to trash ZFS but to understand the real probability of pool loss and how to mitigate against it (apart from the obvious mirrors and off-site backup).
So: how many of you have experienced such a loss and why?
All is well until suddenly it's not and all your data's gone. With ZFS the risk of a catastrophic failure are low but the consequences are devastating.
Right now, on the verge of my first ZFS build, I am not comfortable with that consequence. I know, mirrors, backups etc, but some of the reasons for pool loss seem more and more to me like design flaws. For example: loss of a VDEV = pool loss; corrupted system metadata = pool loss. ZFS does not degrade gracefully.
The purpose of this thread is not to trash ZFS but to understand the real probability of pool loss and how to mitigate against it (apart from the obvious mirrors and off-site backup).
So: how many of you have experienced such a loss and why?