nemesis1782
Contributor
- Joined
- Mar 2, 2021
- Messages
- 105
Hi guys,
I'm looking for some advice on a configuration for my first zPool. The system this relates to is here: https://www.truenas.com/community/t...-on-feasibility-of-first-treunas-setup.91526/
I seperated this since I have a very specific question! zPools and VDEV's.
My current understanding:
- Any zpool consists of 1 or more VDEV's
- the redundancy is handled on the VDEV level
- the VDEV's are striped to create a zPool
- A VDEV which fails will take the whole zPool down without any hope of recovery
- A VDEV has the write performance of a single disk
- A ZPool write speed is ependent on the number of VDEV's
Usage for this zpool:
- Because of the limitations of ZFS I will be using this to house completed series and movies. Once the data is there it should stay there and not be moved around. So little fragmentation should occur
I'll be getting 12x3TB tomorrow and am looking into the following configurations:
- 1 RAIDZ3 11 disks + 1 hot spare, simple straight forward 3 disk redundundancy, bad efficiency
- 2 RAIDZ2 of 6 disks each, better (write) speed, redundancy of 2 to 4 disk redundancy and even worse efficiency since I should keep one more disk lying around to rebuild
- 2 RAIDZ1 5 disks each + 2 hot spare, Same write speed as RAIDZ2 however worse redundancy. Efficiency is about the same.
So now for my questions:
- Having multiple VDEVs in a pool seems risky to me especially on lower RAIDZ levels
- What configuration would you advice for this use case. The data will not be backupped. Loosing the array is a inconvenience but nothing mission critical
- Is there maybe a better configuration?
After this I'll add these zPools:
- Single disk for downloads no redundancy in not meant to store data
- 2x SATA SSD in mirror for VM and such
- 2x m2 SSD for later usage
- A ZPool where series that aren't complete will go
I'm looking for some advice on a configuration for my first zPool. The system this relates to is here: https://www.truenas.com/community/t...-on-feasibility-of-first-treunas-setup.91526/
I seperated this since I have a very specific question! zPools and VDEV's.
My current understanding:
- Any zpool consists of 1 or more VDEV's
- the redundancy is handled on the VDEV level
- the VDEV's are striped to create a zPool
- A VDEV which fails will take the whole zPool down without any hope of recovery
- A VDEV has the write performance of a single disk
- A ZPool write speed is ependent on the number of VDEV's
Usage for this zpool:
- Because of the limitations of ZFS I will be using this to house completed series and movies. Once the data is there it should stay there and not be moved around. So little fragmentation should occur
I'll be getting 12x3TB tomorrow and am looking into the following configurations:
- 1 RAIDZ3 11 disks + 1 hot spare, simple straight forward 3 disk redundundancy, bad efficiency
- 2 RAIDZ2 of 6 disks each, better (write) speed, redundancy of 2 to 4 disk redundancy and even worse efficiency since I should keep one more disk lying around to rebuild
- 2 RAIDZ1 5 disks each + 2 hot spare, Same write speed as RAIDZ2 however worse redundancy. Efficiency is about the same.
So now for my questions:
- Having multiple VDEVs in a pool seems risky to me especially on lower RAIDZ levels
- What configuration would you advice for this use case. The data will not be backupped. Loosing the array is a inconvenience but nothing mission critical
- Is there maybe a better configuration?
After this I'll add these zPools:
- Single disk for downloads no redundancy in not meant to store data
- 2x SATA SSD in mirror for VM and such
- 2x m2 SSD for later usage
- A ZPool where series that aren't complete will go