![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Does ZFS support storage pool like WHS V1?
- Thread starter theinv
- Start date
drescherjm
[H]F Junkie
- Joined
- Nov 19, 2008
- Messages
- 14,933
On top of what danswartz said, ZFS does have pools. Although I am not familiar with WHS so I can't compare the two.
drescherjm
[H]F Junkie
- Joined
- Nov 19, 2008
- Messages
- 14,933
There is also deduplication, compression, encryption...
Personally i do not compare features but look at three essentials, only available in ZFS
1.silent data errors
Statistically every disk gets corrupted datablocks, the larger the disk the more errors you have over time.
On every other (stable) system, you will discover the errors - when its too later to repair -
and when you want to repair, you must dismount the disk and do a offline filecheck (lasts days on TB-pools)
-> ZFS has scrubbing - a online filecheck and repair system, that i run weekly with consumer drives
2. end to end checksum (needed for 1.)
every other (stable) system has checksums, but not os-based over real data but drive internally or controller based.
-> Only ZFS knows really if your data is damaged
3. Copy on write
needed not only for snaps without time delay and without initial space consumption. You need it also
to avoid the usual write hole problem with a conventional raid-controller where your data is inconsistent
in case of a power failure during writes. A battery unit helps but cannot really avoid all problems.
-> with copy on write, a block is written correctly or not at all. On errors goto 2.
Data on ZFS pools are always consistent.
That does not mean, you cannot have data lost but you are always informed when it happens.
Gea
1.silent data errors
Statistically every disk gets corrupted datablocks, the larger the disk the more errors you have over time.
On every other (stable) system, you will discover the errors - when its too later to repair -
and when you want to repair, you must dismount the disk and do a offline filecheck (lasts days on TB-pools)
-> ZFS has scrubbing - a online filecheck and repair system, that i run weekly with consumer drives
2. end to end checksum (needed for 1.)
every other (stable) system has checksums, but not os-based over real data but drive internally or controller based.
-> Only ZFS knows really if your data is damaged
3. Copy on write
needed not only for snaps without time delay and without initial space consumption. You need it also
to avoid the usual write hole problem with a conventional raid-controller where your data is inconsistent
in case of a power failure during writes. A battery unit helps but cannot really avoid all problems.
-> with copy on write, a block is written correctly or not at all. On errors goto 2.
Data on ZFS pools are always consistent.
That does not mean, you cannot have data lost but you are always informed when it happens.
Gea
Last edited: