I've seen this asked so many times here but I wanted to be sure I understand it,

 

I've got a fresh install of 7.0.0-beta.2 with no array drives and everything in zfs pools.

 

• two raidz pools of 5 drives each
• two 2tb NVMe drives in zfs mirror

 

Docker or VMs have not been turned on yet because I want to get the appdata and vdisk locations set first.

 

For dockers, It's my understanding that in settings/docker, I leave vDisk and appdata locations at their defaults (/mnt/userr/system/docker/docker.img and /mnt/user/appdata respectively). and then set the share itself to the cache drive as the primary with a secondary of one of the pools.

 

Its also my understanding that I do the same for settings/VM Manager  leaving Libvirt / VM storage path / Iso storage path 

to their defaults and and setting the shares primary as CACHE or what ever I would want them to be.

 

The way I understand it is that /mnt/user/domains, /mnt/user/isos, /mnt/user/system and /mnt/user/appdata are then links to where ever I have the share primary storage location pointed to.  Is this correct?

 

Thanks guys.

Edited July 16, 20241 yr by jrsphoto
clarify my question

When the services are turned on they will create the shares automatically, if there's a pool called cache they will be created there with cache as primary storage only, if a pool called cache does not exist it will create the shares in the first pool in alphabetical order, if only an array exists the shares will be created there.

Sure, I get that.  I guess my question is really regarding the docker vdisk and appdata locations in settings (and VM settings too)  I seems to me that I don't need to change these because they are just links to what ever location the share points?  make sense? 

6 minutes ago, jrsphoto said:

I seems to me that I don't need to change these because they are just links to what ever location the share points?  make sense? 

Correct, though for some containers, they can perform better with the disk path, for VMs it's not needed since that is done automatically.

2 minutes ago, JorgeB said:

though for some containers, they can perform better with the disk path

As always, thanks JorgeB,  I think you've answered all my question on these forums so far  Your answer is as I suspected.  Are you aware of any videos or posts here that talk about when it might make sense to change these to the physical disk path?  Trying to do a deep dive on some of these edge cases. 

Don't know of any videos or posts, but for any container that handles a lot of data, it may be worth changing, especially for smaller files.