- Minor
On the Shares → User Shares page, Unraid incorrectly shows the orange “some or all files unprotected” warning icon for shares whose cache portion is completely empty and only the share directory (mountpoint) exists under /mnt/cache/<sharename>.
In the screenshot above, ALL "Cache -> Array" shares are empty. There are no files in the cache. "backups" is my test to prove that when the share folder in cache is removed, only then does the status change to protected.
This appears to be because the existence of the directory itself is enough for Unraid to consider the share “present on cache,” even when there are no files there.
This becomes a problem when the share is exported via SMB or NFS: you cannot safely remove that mountpoint directory without possibly causing stale file handle errors on clients who have the folder mounted from unraid. As a result, the GUI permanently shows these shares as “unprotected” even though all data actually resides on the protected array.
Below proves that each share folder in cache is empty, except for tpvl010 which is a cache only share. You'll also note that the "backup" share folder isn't there; as such the share shows as "protected" in the UI.root@tpur001:/mnt/cache# pwd
/mnt/cache
root@tpur001:/mnt/cache# ls -laus
total 16
16 drwxrwxrwx 1 nobody users 78 Oct 26 07:06 ./
0 drwxr-xr-x 16 root root 320 Nov 30 11:56 ../
0 drwxrwxrwx 1 nobody users 0 Oct 26 07:27 qnap/
0 drwxrwxrwx 1 nobody users 0 Oct 30 13:30 tpvl002/
0 drwxrwxrwx 1 nobody users 0 Oct 30 13:48 tpvl003/
0 drwxrwxrwx 1 nobody users 0 Oct 30 12:35 tpvl005/
0 drwxrwxrwx 1 nobody users 18 Nov 12 08:14 tpvl010/
0 drwxrwxrwx 1 nobody users 0 Oct 30 15:41 tpvm001/
root@tpur001:/mnt/cache# du
0 ./tpvl010/FileFlows/Drop/tv-to-hevc
0 ./tpvl010/FileFlows/Drop
4 ./tpvl010/FileFlows/Done
4 ./tpvl010/FileFlows
4 ./tpvl010
0 ./tpvl003
0 ./tpvm001
0 ./tpvl002
0 ./qnap
0 ./tpvl005
20 .
root@tpur001:/mnt/cache# ls *
qnap:
tpvl002:
tpvl003:
tpvl005:
tpvl010:
FileFlows/
tpvm001:
Additionally, shares that are cache-only (tpvl010 above) are always shown as unprotected, even though that is an intentional configuration choice by the user (e.g., scratch/temp shares). This should always be green, or choose a status other then "unprotected" (add new "Cached only" status?)
Expected result:
For shares where all data currently resides on the protected array and the cache pool only has an empty mountpoint directory, the Shares page should:
Treat the share as effectively protected, or
At least not warn that “some or all files are unprotected,” since there are no unprotected files on cache.
For cache-only shares:
The status should reflect that the share is intentionally configured to be unprotected (e.g. neutral icon / info state, or a different label such as “Cache-only (unprotected by design)”).
It should not look like a misconfiguration/partial protection when the configuration is deliberate