Currently have an SSD for “boot-drive” pool, and a 2x12TB for my “main” mirrored data pool. I wanted to keep certain app data pertaining to docker containers + apps separate. I just added one NVMe for that purpose. Would this be best added to the existing “main” pool or should I create a new, completely separate pool just for this NVMe drive?
One idea would be that a Plex, Immich, Jellyfin type container would have the media/photos on the “main” pool, while the compose.yml, app cache, other application-specific related volumes be kept on the NVMe. Not sure if this simply comes down to preference, or if there are any architecture considerations, performance concerns with choosing between the options.
Separate pool, with a single vdev and a single drive for apps.
You cannot add a smaller drive to the existing mirror. And if you add the drive as a single drive vdev to your data pool, it will be used for everything and then loosing this non-redundant drive would mean loosing the entire pool. Oops!
Ahh yes, I completely forgot about that important point, thank you!
I think I’m okay with this because it will be docker related objects, like the networks, images, containers. I will specify via custom compose yaml to store /config /media to target the “main” data pool.
If something were to happen to this NVMe, I have offsite backups of my Ansible roles, Terraform, etc. Basically saved as Infrastructure as code. I just don’t want the apps to consume “main” pool storage with images, whatever various things the container itself needs.
I think you don’t understand: There’s no way to direct specific objects/datasets to specific vdevs within a pool. If you add the M.2 drive as a further vdev in your data pool, apps will spill over the HDD “main storage” and some of the data will be stored on the NVMe.
