December 9, 20232 yr Hi, I've enabled exclusive shares and I have several shares on a ZFS cache pool that show as having exclusive access. Looking at /mnt/user/ in terminal, I do see three folders that are symlinks. From this, I believe my configuration is correct and working, with `appdata` being one of the exclusive access shares. The limited dockers I've tested all seem to start and run. But results are mixed: * `code-server` is able to open exclusive and non-exclusive share folders * `binhex-krusader` set per spaceinvader1's video - only non-exclusive shares are accessible (note the last 3 folders on the left are grayed out) * Ubuntu VM - only non-exclusive shares are accessible via VM mount Here is the section from the VM config: Here is the fstab config and folder view of the mount showing the 3 exclusive folders as unaccessible: It seems like different ways to access the shares are hit or miss. Are these bugs? Something I need to change in the config? Thanks!
December 12, 20232 yr Author Is no on else having similar issues? If there is a fix posted somewhere else, can someone share a link?
December 15, 20232 yr Community Expert A share can't be exclusive if it has any files on the array or any pool other than the designated pool for the share. You can see how much of each disk is used by each share by clicking Compute... for the share on the User Shares page.
December 15, 20232 yr Author 47 minutes ago, trurl said: A share can't be exclusive if it has any files on the array or any pool other than the designated pool for the share. I didn't have an issue getting shares to be recognized as "Exclusive Access". I had trouble with both dockers and the VM being able to use the shares once they were set as exclusive access. Was that not clear from the screenshots?
December 15, 20232 yr Community Expert None of your screenshots show which disks have files for the shares. Just changing the settings for a share won't result in any files being moved. 3 hours ago, trurl said: You can see how much of each disk is used by each share by clicking Compute... for the share on the User Shares page. However, I don't think it will allow you to make a share exclusive if it does have files in other places.
December 15, 20232 yr Author Sorry if my original post wasn't clear. I have 7 shares, and with exclusive shares setting enabled, 3 of them became exclusive shares. Exclusive: appdata, media, pictures Non-exclusive: domains, isos, system, zfs-backup. In the top image (binhex-krusader), the left side of the window shows a folder view of /mnt/user exposed to the docker (all of the shares). The three exclusive shares are shown with a different icon and are not accessible as folders in the docker container. The non-exclusive folders are accessible and behave as expected. For the Ubuntu VM, the situation is similar. I manually expose /mnt/user to the VM, but only the non-exclusive folders show as folders, the exclusive ones have an icon with an "X" and don't work (in the bottom image). I've tried both 9p and virtiofs and had the same results. Note - I don't expect any files to move automatically, I was expecting to be able to use the docker/VM to test if the write speed was improved (via drag-n-drop in the systems) skipping FUSE. Hopefully this is clearer? Are you successfully using exclusive shares? If so, can you describe what you are doing that works?
December 16, 20232 yr 5 hours ago, stottle said: Are you successfully using exclusive shares? If so, can you describe what you are doing that works? Pass them through individually rather than (or in addition to) using the /mnt/user directory.
December 16, 20232 yr Author 10 hours ago, L0k1 said: Pass them through individually Ok. That does make the folders accessible. But seems only slightly better than mounting from /mnt/cache/<share>. Edited December 16, 20232 yr by stottle
January 30, 20251 yr If anyone was still wondering, the reason why the exclusive shares are not accessible via Krusader is because they are links to folders outside of /mnt/user, and you have only mounted /mnt/user into the krusader docker container. If you instead mount /mnt on your krusader container, you will be able to access your exclusive shares.
April 5, 20251 yr On 1/30/2025 at 3:28 PM, gazpachoking said: If anyone was still wondering, the reason why the exclusive shares are not accessible via Krusader is because they are links to folders outside of /mnt/user, and you have only mounted /mnt/user into the krusader docker container. If you instead mount /mnt on your krusader container, you will be able to access your exclusive shares. This is the answer I was searching for that led me to this thread thank you!
April 5, 20251 yr Community Expert On 1/30/2025 at 10:28 AM, gazpachoking said: Krusader Simpler and safer to use Dynamix File Manager.
December 25, 2025Dec 25 On 1/30/2025 at 5:28 PM, gazpachoking said:If anyone was still wondering, the reason why the exclusive shares are not accessible via Krusader is because they are links to folders outside of /mnt/user, and you have only mounted /mnt/user into the krusader docker container. If you instead mount /mnt on your krusader container, you will be able to access your exclusive shares.This is very bad news...I'd like a container to have access to a specific folder inside a user share, residing on a pool drive...With the above conclusion, it's either I'm exposing the whole /mnt mount point to the container, or disable the Exclusive Shares and lose the performance benefit of bypassing FUSE...In my scenario, it seems I should just map the folder from the pool drive itself directly to the container, instead of mapping through /mnt/userOn 1/30/2025 at 5:28 PM, gazpachoking said:If anyone was still wondering, the reason why the exclusive shares are not accessible via Krusader is because they are links to folders outside of /mnt/user, and you have only mounted /mnt/user into the krusader docker container. If you instead mount /mnt on your krusader container, you will be able to access your exclusive shares.This is very bad news...I'd like a container to have access to a specific folder inside a user share, residing on a pool drive...With the above conclusion, it's either I'm exposing the whole /mnt mount point to the container, or disable the Exclusive Shares and lose the performance benefit of bypassing FUSE...In my scenario, it seems I should just map the folder from the pool drive itself directly to the container, instead of mapping through /mnt/user 🤔
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.