ZFS can be a little inflexible on things like expanding your pool with more drives but that's a tradeoff I'll cheerfully make. If your operating system drive fails, getting your data back literally consists of installing on a new drive and then typing zfs import. It's just an incredibly robust system.Īlso, it is very robust in other ways too. ZFS in a raid with checksums literally detect and correct that quietly. With larger and larger drives the certainty of that happening goes up. You should Google up some stuff about silent data corruption. Why is that? Why is ZFS so preferred over any other traditional data keeping methods? Better yet, I have a mirror to copy over the corrupted file, keeping my data integrity.įrom what I understand (if i'm even understanding this correctly), The same scenario will result in the whole thing crumbling apart with all my data gone. If I simply use redundancy RAID mirror, if one has a partial corruption possibly causing a few of my photos to become corrupted, I'd be very sour but at least I still have the entire family photos, business documents, personal documents all still there. Yes, the automatic integrity checksum, flexible vdev management and all that is great, but why does it have to " If any VDev in a zpool is failed, you will lose the entire zpool with no chance of partial recovery. I simply don't understand the advantage of the system.
#Freenas volume manager set up zfs pool how to#
I believe I now sort of know how to do everything mostly, the only thing preventing me from pulling the trigger is ZFS. This is my first time setting up a home server, and I've been doing as much reading as possible on how to design my storage setups.
0 kommentar(er)
