melbournemac
Dabbler
- Joined
- Jan 21, 2017
- Messages
- 20
Hi,
Expect to reach 80% utilisation in one of the storage pools late this year. Thought I'd better start planning on how to address. The pool consists of 3 vdevs with each vdev consisting of a mirrored pair of 6TB WD Red (CMR) drives. The pool is mainly used for SMB shares, but also contains the system dataset and storage for one VM (running under iohyve).
Given the case is getting full and 12 & 14TB drives are now available, was thinking of reducing the # vdevs in the pool, instead of just increasing the capacity of each vdev or adding another vdev.
Having only ever increased disk capacity or increased the number of vdevs in a pool, I thought it pertinent to ask some questions
thanks,
Steve
Current Specs (I know it's very old hardware - expect to update motherboard, CPU, RAM sooner rather than later)
Expect to reach 80% utilisation in one of the storage pools late this year. Thought I'd better start planning on how to address. The pool consists of 3 vdevs with each vdev consisting of a mirrored pair of 6TB WD Red (CMR) drives. The pool is mainly used for SMB shares, but also contains the system dataset and storage for one VM (running under iohyve).
Given the case is getting full and 12 & 14TB drives are now available, was thinking of reducing the # vdevs in the pool, instead of just increasing the capacity of each vdev or adding another vdev.
Having only ever increased disk capacity or increased the number of vdevs in a pool, I thought it pertinent to ask some questions
- Is it still true that you cannot remove a vdev from a pool?
- is the recommended approach still to (taken from here)?
- Add additional disks (burn in / long smart test)
- Create new pool comprising of new disks
- Create snapshot of existing pool
- perform zfs send - receive of snapshot to the new pool
- shutdown NFS / SMB etc to stop writes
- take another snapshot of existing pool and incrementally send to new pool
- Mark existing pool as read only
- Export pools
- Import new pool, renaming it to the existing pool's name
- start NFS / SMB services
thanks,
Steve
Current Specs (I know it's very old hardware - expect to update motherboard, CPU, RAM sooner rather than later)
Version: TrueNAS-12.0-U1.1 (as of 27-Jan-2021)
Motherboard: Intel S5500HCV
CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
Memory: 24GB DDR3 ECC RAM (6 x 4GB)
HBA: LSI SAS2008-8I SATA 9211-8i
Boot: Samsung SSD 750 EVO 120GB
Pool1: 3 vdevs, each a mirrored pair of 6TB WD Red (CMR)
Pool2: 1 vdev, single disk (not important / can be destroyed without impact)