November 26, 20205 yr I just noticed this warning on my server: Share cache is identically named to a disk share While there *may be* (doubtful) valid use cases for having a share named identically to a disk share, this is only going to cause some confusion as if disk shares are enabled, then you will have duplicated share names, and possibly if disk shares are not enabled, then you might not be able to gain access to the share. This is usually caused by moving the contents of one disk to another (XFS Conversion?) and an improperly placed slash. The solution is to move the contents of the user share named cache to be placed within a validly named share. Ask for assistance on the forums for guidance on doing this. I checked the Shares tab on the console and I do not see a share named "cache." I do have a device named "cache" on the Main tab. Thoughts?
November 27, 20205 yr Author 2 hours ago, jonathanm said: Diagnostics zip file? I noticed I have a /mnt/user/cache directory. Maybe that is it? tower-diagnostics-20201126-1904.zip
November 27, 20205 yr 7 minutes ago, kennelm said: I noticed I have a /mnt/user/cache directory. Maybe that is it? yes
November 27, 20205 yr Author 26 minutes ago, Squid said: yes Not sure how that got there, but it was mostly empty, so I renamed it to see what happens. Meanwhile, the warning went away.
November 27, 20205 yr Check any docker apps to see if they reference /mnt/user/cache instead of /mnt/cache
November 27, 20205 yr Author 50 minutes ago, Squid said: Check any docker apps to see if they reference /mnt/user/cache instead of /mnt/cache Good idea. None found. It very well could have been a docker container I misconfigured, tested, and then deleted.
Archived
This topic is now archived and is closed to further replies.