Some shares are symlinks, and therefore not always accessable

[TallMan206]

Hi,

Some of my 'shares' are symlinks, and this gives problems when trying to access them from for example Krusader.

Now I installed a Windows 11 VM, with spaceinvaderone's video with the VirtIO-FS service to access the Unraid server from explorer in WIn 11 to process 3D blurays with BD3D2MK3D, but i cannot reach the files on the downloads share.

 

Situation:

The accessable shares are on the array, but the symlink shares are all on my ssd-pool, which is a separate pool of ssd's to hold my appdata and downloads. How come those are symlinks, while the shares are created from the share menu in Unraid, and i just selected the ssdpool instead of the array?

 

Also, the shares on the ssd pool say: exclusive access. I cannot change that. The shares on the array do NOT say that. 

 

What is the reason for this symlinks?

 

[Kilrah]

1 minute ago, TallMan206 said:

Also, the shares on the ssd pool say: exclusive access. I cannot change that.

Global Share Settings -> Permit Exclusive shares

 

Exclusive shares bypass FUSE (unraid's system that collates array disks and pools) and thus increase performance significantly.

[TallMan206]

2 minutes ago, Kilrah said:

Global Share Settings -> Permit Exclusive shares

 

Exclusive shares bypass FUSE (unraid's system that collates array disks and pools) and thus increase performance significantly.

Exclusive shares are on. 

[TallMan206]

For now I solved it to run the shares to cache first, 2nd pool the ssd-pool, but I like to find a way to directly put it on the ssdpool without symlinks

[Kilrah]

1 hour ago, TallMan206 said:

Exclusive shares are on

Well that's the point, if you don't want them turn that off.

 

But yes setting primary ssdpool, secondary array, mover array->ssdpool would disable exclusive for that share and never actually use the array unless the pool is full.