July 18, 201510 yr If I click the "Log" button in the web UI I see a ton of these messages: Jul 18 00:01:46 Tower shfs/user: share cache full Jul 18 00:01:48 Tower shfs/user: share cache full Jul 18 00:01:48 Tower shfs/user: share cache full Jul 18 00:01:49 Tower shfs/user: share cache full Jul 18 00:01:49 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:54 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Both googling and searching the forums didn't bring up anything. Should I be worried about this? What does it mean? Thanks!
July 19, 201510 yr Author Filesystem Size Used Avail Use% Mounted on tmpfs 128M 79M 50M 62% /var/log /dev/sda1 7.5G 208M 7.3G 3% /boot /dev/md1 4.6T 3.8T 776G 84% /mnt/disk1 /dev/md2 4.6T 3.8T 841G 82% /mnt/disk2 /dev/md3 4.6T 3.7T 918G 81% /mnt/disk3 /dev/md4 4.6T 4.2T 428G 91% /mnt/disk4 /dev/md5 4.6T 2.6T 2.1T 56% /mnt/disk5 /dev/md6 4.6T 2.8T 1.8T 62% /mnt/disk6 /dev/sdb1 236G 45G 187G 20% /mnt/cache shfs 28T 21T 6.7T 76% /mnt/user0 shfs 28T 21T 6.9T 76% /mnt/user /dev/loop0 10G 5.1G 3.8G 58% /var/lib/docker /dev/loop1 1.8M 85K 1.6M 6% /etc/libvirt
July 19, 201510 yr Stop and restart the array to create a brand new User Shares system, to see if that stops them. Check the full syslog, where the messages begin. You generally only want to see the very beginning of an error condition, not all of the garbage that follows while still in an error state. Perhaps it starts when the Mover last run?
July 19, 201510 yr Author Thanks! Restarting the array fixed the messages. If they happen again I'll track them back to the start in syslog.
January 9, 20242 yr I was having the same problem. For me it turned out to be that I had accidentally set one of my shares "Minimum free space:" to 300GB instead of the intended 30GB.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.