4 ms·
Huh. I hadn't even considered that it would be possible to assign partitions to the vdevs instead of the entirety of the drive. Though I guess it does make sens
by ziml77 5y ago
Huh. I hadn't even considered that it would be possible to assign partitions to the vdevs instead of the entirety of the drive. Though I guess it does make sense that you can, otherwise you wouldn't be able to use a drive participating in a vdev as a boot device.
I don't need the feature that badly though. It's just something that's interested me about Unraid (and most consumer NAS devices actually), especially since I'm running 4 2TB drives and 2 3TB drives as a single RAIDZ2 vdev in my home TrueNAS setup.
- magicalhippo 5y ago> I hadn't even considered that it would be possible to assign partitions to the vdevs instead of the entirety of the drive. You can even use files[1]! Mostly available for testing though. It would be nice with a bit more flexibility with regards to the underlying storage, hence this concept. I tested it in a VM and it works fine, just slow when the underlying disks gets trashed. Mostly noticeable on heavy writes and scrubs. Should work fine on SSDs though, and might possibly even be a boon to very fast NVMe drives (increasing concurrency). [1]: https://openzfs.github.io/openzfs-docs/man/7/zpoolconcepts.7.html https://openzfs.github.io/openzfs-docs/man/7/zpoolconcepts.7...