- Closed
Say I have two user shares, a and b. a has the cache set to "yes," b has the cache set to "off."
I have a file, foo, on a which is currently on the cache, and I run the following command:
mv /mnt/user/a/foo /mnt/user/b/
foo is instantly moved to share b, however, the file itself is still on the cache. If I check the contents of my cache drive, I see `/mnt/cache/b/foo`. Since the cache behaviour of share b is set to "no," this file is now stuck on the cache, unless I manually set b to "yes" for the cache, invoke the mover, then set it back to "no." Without this manual intervention, my cache drive would fill up endlessly.
Is this intended behaviour, or a bug?