Hey,

I'm guessing its a visual bug, on 7.1.4 atm.

I'm just doing a lot of plex recahcing and cleaning up metadata, one thing I've noticed my db tends to hang every now and then (put a script in place for now to just reboot container)

but also during this I found some reccomendation to change appdata path from /mnt/user/appdata/container to /mnt/cache/appdata/container.

I have a zfs pool with all my appdata on it now, stopped container in question, ran the cache writes cmd

sync; echo 1 > /proc/sys/vm/drop_caches

and adjusted the container path, however in docker view in unraid I can still see the appdata mount path being set to user path, is this expected and just unraid? I'm in middle of more cleanup tasks and it seems to perform better than before.

The /mnt/user/sharename type path is a logical consolidated view that will show the files in that share regardless of where they are located (i.e. on the array or any pool). Files will also appear under the physical device they are located on if looking directly there.

43 minutes ago, itimpi said:

The /mnt/user/sharename type path is a logical consolidated view that will show the files in that share regardless of where they are located (i.e. on the array or any pool). Files will also appear under the physical device they are located on if looking directly there.

2nd part I get, and yeah the files only exist on the nvmezfs pool, with no secondary storage.

1st part though, so are you saying that regardless of the path mount I choose, unraid will always display it as a user share path? despite it being told to use a direct disk (pool in this case) in the container build config and seemingly using the direct disk path? I'm happy to accept that as the performance of the plex appdata has increased substantially, going from few mb/s at best to 200mb/s peaks, in app performance is reflecting that also

That's an outdated practice using direct disk paths now. Instead what you should do is go into the global share settings and set "Permit Exclusive Shares: Yes" this will achieve the samething but allow you to use /mnt/user/... instead of /mnt/pool_name/... while keeping the performance of the direct disk operation.

Edited October 28, 2025Oct 28 by MowMdown

5 minutes ago, MowMdown said:

That's an outdated practice using direct disk paths now. Instead what you should do is go into the global share settings and set "Permit Exclusive Shares: Yes" this will achieve the samething but allow you to use /mnt/user/... instead of /mnt/pool_name/...

Ahh I see, yes that sounds like what I'm trying to achieve with the /mnt/pool/ paths, I will let plex finish off the library its doing and give that a try, thanks. I should read patch notes more frequently, seems to have been in place back in 6.12. I was mostly testing stuff on plex as thats impact the most atm but I was planning on changing other containers, with this global change should be simpler and easier.

Thanks for the info.

Once you've enabled that setting, you should see this on the share setting page:

If this says "No" you still may have files on other disks or pools, you will need to remedy that first.

Also, on the share page itself you will see little triangles next to the pool name the share is located: In this example, the bottom share is cache exclusive the top and middle ones are not.

Edited October 28, 2025Oct 28 by MowMdown

47 minutes ago, Mizerka said:

1st part though, so are you saying that regardless of the path mount I choose, unraid will always display it as a user share path

Not quite. I am saying that all top level folders on any drive will show up as User Shares. That does not stop you using a physical path - just expect any particular file to show up under both paths as they are just different views.

As was mentioned at one point it was recommended to use a physical path to get maximum performance by by-passing the Fuse layer in Unraid. Nowadays using an Exclusive share also by-passes Fuse and gets the same performance as the physical path.

>all top level folders on any drive will show up as User Shares

Ah I get you now, yes makes sense.

Thanks both, I will get exclusive shares configured later on today and see how it goes

seems good so far, shares picked up as exclusive, interestingly, docker template now forces itself to be /mnt/pool/path even when trying to force it via /mnt/user/path. docker view correctly shows /mnt/pool also. cant believe I ran plex without this for years, metadata and scanning is inanely faster now.

6 hours ago, Mizerka said:

interestingly, docker template now forces itself to be /mnt/pool/path even when trying to force it via /mnt/user/path.

Take a look at Settings -> Docker Settings -> Default appdata storage location. It defaults to /mnt/user/appdata/, I'm guessing you changed it to use the poolname at some point

21 hours ago, ljm42 said:

Take a look at Settings -> Docker Settings -> Default appdata storage location. It defaults to /mnt/user/appdata/, I'm guessing you changed it to use the poolname at some point

no still on /mnt/user/appdata, it works so its probably fine, just odd behaviour, not seen it auto change path mid navigation like that. if I wasnt clear enough, if I go into container edit, change any path, start going level by level into appdata (now exclusive share, on a zfs pool), /mnt/user/appdata/ works fine, then when I go a level deeper inside the appdata, say binhex-plex/ it will rewrite the path to /mnt/nvmezfs/appdata/binhex-plex/

Im pretty sure it's normal due to it being technically a disk share at that point unraid is just chainging it in the webgui. Ive noticed this behavior as well.

FWIW, Tried several ways to replicate this and can't do it. Only thing I can possibly think of is if you happen to have Authoring Mode selected in Settings - Docker and then when editing the container hit "Save" instead of "Apply".

Glad it's working, but if you ever see this again, posting the docker run command would've given the path that is actually being used.