limetech wrote the following,

Quote

For exclusive shares we made an implementation change.  We found issues using bind-mounts with ZFS pools with internal nested child datasets.  To overcome this problem, symlinks are created in /mnt/user instead.  For example, for an exclusive share named "myshare" which exists only on "mypool" this symlink is genreated:

 

/mnt/user/myshare -> /mnt/mypool/myshare

 

 

Shouldnt this be     /mnt/mypool/myshare -> /mnt/user/myshare    

or am i just not reading this correctly ?

Bob

 

 

 

additional question,  in the docker config, it appears that you can not select a zfspool/ as a appdata default storage location,  is this by design or a bug ?

docker vdisk can be set to zfspool, but not appdata

 

You can use zfs storage for appdata, does the appdata folder exist?

 

yes appdata does exist (on the pool not the array)

when i select the dropdown for default appdata location, it only shows shares i have on the array

Use /mnt/user as path.

 

Disk path also works for me.

I set Enable User Share Assignment to no, due to I was having issues with RC5 where the data in the user share could be different then  what was in the dataset disk share.

that is how i found that appdata path could not be set to a zpool if enable share assignment is set to no. but you can set the docker vdisk location,

Possibly the  issue  with different data in user share and the pool dataset no longer an issue with RC6 ? sounds like some changes where made regarding using bind-mounts in zfs.

 

 

14 minutes ago, bobC said:

Possibly the  issue  with different data in user share and the pool dataset no longer an issue with RC6 ?

Correct, with rc6 you can use exclusive access and nested datasets together.

perfect!, then that solves my initial issue 

thanks for the help on this

 

Bob