February 23, 201511 yr unRAID OS Version: 6b14 Description: Confusing empty cache share How to reproduce: Create a folder on a drive called "cache" and then make that drive the cache drive Expected results: //server/cache should be the contents of /mnt/cache Actual results: /server/cache shows the the contents of /mnt/cache/cache and a cache.cfg is created to further confuse things Other information: A folder in the root of the cache drive called cache should be ignored or not take priority Original discussion http://lime-technology.com/forum/index.php?topic=38334.0
February 23, 201511 yr I recall helping another user with this not long ago. It is expected behavior with the way unRAID makes any root folder a user share. Probably the same would happen if you created a root folder named disk1 for example.
February 23, 201511 yr unRAID OS Version: 6b14 Description: Confusing empty cache share How to reproduce: Create a folder on a drive called "cache" and then make that drive the cache drive Expected results: //server/cache should be the contents of /mnt/cache Actual results: /server/cache shows the the contents of /mnt/cache/cache and a cache.cfg is created to further confuse things Other information: A folder in the root of the cache drive called cache should be ignored or not take priority Original discussion http://lime-technology.com/forum/index.php?topic=38334.0 I wonder if we should just prohibit the creation of shares with a name that overlaps with a system defined name like cache. Will discuss with Tom.
February 23, 201511 yr I wonder if we should just prohibit the creation of shares with a name that overlaps with a system defined name like cache. Will discuss with Tom. Creating a user share through the webGUI is not the only way to make this happen. Probably most of the time it happens because someone has specified a path like /mnt/user/cache or /mnt/user/disk1 or something like that somewhere.
February 23, 201511 yr Author unRAID OS Version: 6b14 Description: Confusing empty cache share How to reproduce: Create a folder on a drive called "cache" and then make that drive the cache drive Expected results: //server/cache should be the contents of /mnt/cache Actual results: /server/cache shows the the contents of /mnt/cache/cache and a cache.cfg is created to further confuse things Other information: A folder in the root of the cache drive called cache should be ignored or not take priority Original discussion http://lime-technology.com/forum/index.php?topic=38334.0 I wonder if we should just prohibit the creation of shares with a name that overlaps with a system defined name like cache. Will discuss with Tom. Agreed but as trurl says this would have to be both in the front end (i.e. this share is reserved error) and in the backend (i.e. the bit that caught me out)
Archived
This topic is now archived and is closed to further replies.