I often times get shares that I list as Cache Only shares to show up in my /mnt/user0 folder.

 

Then when the mover runs, it blows up my error logs and often times I have to reboot my server because it stops responding. It looks like this:

 

Jul 26 04:56:26 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder/logs (28) No space left on device
Jul 26 04:56:27 Tower last message repeated 9 times
Jul 26 04:56:27 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder/cache (28) No space left on device
Jul 26 04:56:58 Tower last message repeated 387 times
Jul 26 04:57:18 Tower last message repeated 261 times
Jul 26 04:57:18 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder/db_backup (28) No space left on device
Jul 26 04:57:19 Tower last message repeated 11 times
Jul 26 04:57:19 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder2 (28) No space left on device
Jul 26 04:57:50 Tower last message repeated 377 times
Jul 26 04:58:51 Tower last message repeated 838 times
Jul 26 04:59:07 Tower last message repeated 206 times
Jul 26 04:59:08 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder3 (28) No space left on device
Jul 26 04:59:39 Tower last message repeated 398 times
Jul 26 05:00:40 Tower last message repeated 780 times
Jul 26 05:01:41 Tower last message repeated 782 times
Jul 26 05:02:42 Tower last message repeated 797 times
Jul 26 05:03:28 Tower last message repeated 629 times
Jul 26 05:03:28 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder4 (28) No space left on device
Jul 26 05:03:59 Tower last message repeated 377 times
Jul 26 05:04:07 Tower last message repeated 103 times
Jul 26 05:04:07 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder5 (28) No space left on device
Jul 26 05:04:38 Tower last message repeated 388 times
Jul 26 05:05:39 Tower last message repeated 772 times
Jul 26 05:06:40 Tower last message repeated 763 times
Jul 26 05:07:41 Tower last message repeated 766 times
Jul 26 05:08:42 Tower last message repeated 776 times
Jul 26 05:09:43 Tower last message repeated 809 times
Jul 26 05:10:44 Tower last message repeated 974 times
Jul 26 05:11:45 Tower last message repeated 924 times
Jul 26 05:12:46 Tower last message repeated 845 times
Jul 26 05:13:47 Tower last message repeated 658 times
Jul 26 05:14:48 Tower last message repeated 653 times
Jul 26 05:15:49 Tower last message repeated 768 times
Jul 26 05:16:50 Tower last message repeated 795 times
Jul 26 05:17:00 Tower last message repeated 150 times

 

 

I really don't know what is causing that share to be created on user0, but if I move the one or two files that went to user0 back to my cache drive and delete the share off of the user0 it seems to work right. Any ideas?

 

I'm going to update tonight, but I am on rc12a currently.

 

It seems to happen out of the blue. There is no mention of user0 other than it being initialized, then once the server is up it just starts doing this. I will get hundreds of thousands of errors logged

I often times get shares that I list as Cache Only shares to show up in my /mnt/user0 folder.

 

Then when the mover runs, it blows up my error logs and often times I have to reboot my server because it stops responding. It looks like this:

 

Jul 26 04:56:26 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder/logs (28) No space left on device
Jul 26 04:56:27 Tower last message repeated 9 times
Jul 26 04:56:27 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder/cache (28) No space left on device
Jul 26 04:56:58 Tower last message repeated 387 times
Jul 26 04:57:18 Tower last message repeated 261 times
Jul 26 04:57:18 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder/db_backup (28) No space left on device
Jul 26 04:57:19 Tower last message repeated 11 times
Jul 26 04:57:19 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder2 (28) No space left on device
Jul 26 04:57:50 Tower last message repeated 377 times
Jul 26 04:58:51 Tower last message repeated 838 times
Jul 26 04:59:07 Tower last message repeated 206 times
Jul 26 04:59:08 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder3 (28) No space left on device
Jul 26 04:59:39 Tower last message repeated 398 times
Jul 26 05:00:40 Tower last message repeated 780 times
Jul 26 05:01:41 Tower last message repeated 782 times
Jul 26 05:02:42 Tower last message repeated 797 times
Jul 26 05:03:28 Tower last message repeated 629 times
Jul 26 05:03:28 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder4 (28) No space left on device
Jul 26 05:03:59 Tower last message repeated 377 times
Jul 26 05:04:07 Tower last message repeated 103 times
Jul 26 05:04:07 Tower shfs/user0: shfs_mkdir: assign_disk: apps/folder5 (28) No space left on device
Jul 26 05:04:38 Tower last message repeated 388 times
Jul 26 05:05:39 Tower last message repeated 772 times
Jul 26 05:06:40 Tower last message repeated 763 times
Jul 26 05:07:41 Tower last message repeated 766 times
Jul 26 05:08:42 Tower last message repeated 776 times
Jul 26 05:09:43 Tower last message repeated 809 times
Jul 26 05:10:44 Tower last message repeated 974 times
Jul 26 05:11:45 Tower last message repeated 924 times
Jul 26 05:12:46 Tower last message repeated 845 times
Jul 26 05:13:47 Tower last message repeated 658 times
Jul 26 05:14:48 Tower last message repeated 653 times
Jul 26 05:15:49 Tower last message repeated 768 times
Jul 26 05:16:50 Tower last message repeated 795 times
Jul 26 05:17:00 Tower last message repeated 150 times

 

 

I really don't know what is causing that share to be created on user0, but if I move the one or two files that went to user0 back to my cache drive and delete the share off of the user0 it seems to work right. Any ideas?

 

I'm going to update tonight, but I am on rc12a currently.

 

It seems to happen out of the blue. There is no mention of user0 other than it being initialized, then once the server is up it just starts doing this. I will get hundreds of thousands of errors logged

user0 is the "view" of the user-share file system WITHOUT the contents of the cache drive merged in.

 

It is used by the "mover" script as the destination to move files from the cache drive.

 

Apparently, one of the hard disks in your array is out of space, or has file-system corruption that make it appear out of space.

None of the disks are full. It creates the cache only share on user0 and nothing can right to it because it is cache only share there is no space on my array allocated to the cache only drive

None of the disks are full. It creates the cache only share on user0 and nothing can right to it because it is cache only share there is no space on my array allocated to the cache only drive

ok, I think I understand better.

 

Does your "cache only" directory exist on any of your data disks?

Normally no. There Is no cache only share on my array. But right when the server starts up it seems to write a single file over there and the. The mover is thrown off

Normally no. There Is no cache only share on my array. But right when the server starts up it seems to write a single file over there and the. The mover is thrown off

What file is written there?

Post the output of

ls -laR  /mnt/user/cache_only_share_name

 

(using your correct cache_only_share_name)

The file was CouchPotato's Settings.conf. Which I use a plugin to unraid to install couchpotato on startup and it is pointed directly to /mnt/cache/Applications which is my share

The file was CouchPotato's Settings.conf. Which I use a plugin to unraid to install couchpotato on startup and it is pointed directly to /mnt/cache/Applications which is my share

Sounds more like a misbehaving add-on.

I just still found it weird, because I always told all my plugins to go to /mnt/cache and never told it /mnt/user0 even exists. I have rebooted a few times and the issue seems resolved. Hopefully it just doesn't come back.