Jump to content
nuhll

High CPU /usr/local/sbin/shfs /mnt/user -disk

23 posts in this topic Last Reply

Recommended Posts

Hi guys,

i thought my 2 camera setup is taking high cpu, but i thought, lets stop it and look how much cpu unraid uses without xeoma docker running.

 

Its still about 30% ~~

 

/usr/local/sbin/shfs /mnt/user -disk 1023 204800000 -o noatime,big_writes,allow_other -o remember=0

 

htop shows this, i cant really tell what this is, its probably something legit, but i would like to know what this does..

 

via google i just found something about shares open... but atm there is no share open (smb), ofc some dockers are running, but if i look at open files plugin, i dont see such a thing.

 

My best guess would be its plex, but its on cache not on /mnt/user Oo


If i read htop correct, this process is running since last restart and is taking since then 100% of one core :)

 

Quote
udevd 1156 Kill 4 0 /lib/modules/4.14.13-unRAID/modules.builtin.bin
/lib/modules/4.14.13-unRAID/modules.symbols.bin
/lib/modules/4.14.13-unRAID/modules.alias.bin
/lib/modules/4.14.13-unRAID/modules.dep.bin
shfs 4050 Kill 100 100 /mnt/cache/appdata/plexrequests/db/mongod.lock
/mnt/cache/appdata/plexrequests/db/WiredTiger.lock
/mnt/cache/appdata/plexrequests/db/WiredTiger.wt
/mnt/cache/appdata/plexrequests/db/journal/WiredTigerLog.0000000025
/mnt/cache/appdata/plexrequests/db/collection-20-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/WiredTigerLAS.wt
/mnt/cache/appdata/plexrequests/db/sizeStorer.wt
/mnt/cache/appdata/plexrequests/db/_mdb_catalog.wt
/mnt/cache/appdata/plexrequests/db/collection-15-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/collection-17-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/collection-24-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/collection-29-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/collection-12-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/collection-27-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/collection-0--4130828054873547616.wt
/mnt/cache/appdata/plexrequests/db/collection-2-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/collection-0-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/index-1-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/diagnostic.data/metrics.2018-01-13T19-26-51Z- ...
/mnt/cache/appdata/duplicati/Duplicati-server.sqlite
/mnt/cache/appdata/plexrequests/db/index-16-1182081791667001860.wt
/mnt/cache/appdata/duplicati/control_dir_v2/lock_v2
/mnt/cache/appdata/plexrequests/db/index-8-1182081791667001860.wt
/mnt/cache/appdata/headphones/logs/headphones.log
/mnt/cache/appdata/plexrequests/db/index-28-1182081791667001860.wt
/mnt/cache/appdata/radarr/nzbdrone.db
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/radarr/nzbdrone.db-shm
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/radarr/logs.db
/mnt/cache/appdata/radarr/logs.db-wal
/mnt/cache/appdata/radarr/logs.db-shm
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/Sonarr/nzbdrone.db
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
/mnt/cache/appdata/Sonarr/nzbdrone.db-wal
/mnt/cache/appdata/Sonarr/nzbdrone.db-shm
/mnt/cache/appdata/Sonarr/nzbdrone.db
/mnt/cache/appdata/radarr/nzbdrone.db-wal
/mnt/cache/appdata/Sonarr/nzbdrone.db-wal
/mnt/cache/appdata/plexrequests/db/index-9-1182081791667001860.wt
/mnt/cache/appdata/Sonarr/logs.db
/mnt/cache/appdata/Sonarr/logs.db-shm
/mnt/cache/appdata/Sonarr/logs.db
/mnt/cache/appdata/Sonarr/logs.db-wal
/mnt/cache/appdata/plexrequests/db/index-21-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/index-22-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/index-25-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/index-23-1182081791667001860.wt
/mnt/cache/appdata/plexrequests/db/index-1--4130828054873547616.wt
/mnt/cache/appdata/radarr/logs.db
/mnt/cache/tmp/dup-d7ed66c6-c728-450f-9dd5-eeb13f6496a4
/mnt/cache/tmp/dup-fa712d0c-e1fa-47fc-b064-eec28ea425c5
/mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server ...
dockerd 4349 Kill 13 13 /var/lib/docker/volumes/metadata.db
/var/lib/docker/builder/fscache.db
/var/lib/docker/containers/f8a0c1d6badabee7df34bcfe12bfee05d12e9b24823e2076494fe ...
/var/lib/docker/containers/2773c3c3973bda0823de9a3f707380f57897584dace5d74285991 ...
/var/lib/docker/containers/4b466d5d8ab2cff99f38adf6393e324ab2dc26b179b49da90b098 ...
/var/lib/docker/containers/e4562047798acd27288ba7db6a3170ce145c5ddd15fb0d244d8a0 ...
/var/lib/docker/containers/1e39b5376f8268091dab2ad7d5bcbcef9bb2b46a2ce54ada9b3f3 ...
/var/lib/docker/containers/88a0c3db9926478ca8eebd3d0667d9dec2ff9e1f459dc96281743 ...
/var/lib/docker/containers/6fc171a0b37eb6b62c24711db8e2fbc2071e7f993a30c9abc7ee5 ...
/var/lib/docker/containers/5c345105479aaffcb96629d79f9a9dc72c2f07479d14b375ca6cd ...
/var/lib/docker/containers/547d732436415103243eec92dedbf3889f2f38fcba473fd6a8008 ...
/var/lib/docker/containers/2b5bea893485742b1c0a135bf0e39d858e989ab3bb09a9d95a71d ...
/var/lib/docker/containers/a7b4ebb087365c8693f650f21ff9a1a0ff57514ee3b3eac819697 ...
nginx 4924 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4929 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4930 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4931 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4932 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4933 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4934 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4935 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4936 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4937 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4938 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4939 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4940 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4941 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4942 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4943 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4944 Kill 2 2 /data/logs/access.log
/data/logs/error.log
nginx 4945 Kill 2 2 /data/logs/access.log
/data/logs/error.log
mongod 5624 Kill 29 28 /config/db/mongod.lock
/config/db/WiredTiger.lock
/config/db/WiredTiger.wt
/config/db/journal
/config/db/journal/WiredTigerLog.0000000025
/config/db/collection-20-1182081791667001860.wt
/config/db/WiredTigerLAS.wt
/config/db/sizeStorer.wt
/config/db/_mdb_catalog.wt
/config/db/collection-15-1182081791667001860.wt
/config/db/collection-17-1182081791667001860.wt
/config/db/collection-24-1182081791667001860.wt
/config/db/collection-29-1182081791667001860.wt
/config/db/collection-12-1182081791667001860.wt
/config/db/collection-27-1182081791667001860.wt
/config/db/collection-0--4130828054873547616.wt
/config/db/collection-2-1182081791667001860.wt
/config/db/collection-0-1182081791667001860.wt
/config/db/diagnostic.data/metrics.2018-01-13T19-26-51Z-00000
/config/db/index-1-1182081791667001860.wt
/config/db/index-16-1182081791667001860.wt
/config/db/index-8-1182081791667001860.wt
/config/db/index-28-1182081791667001860.wt
/config/db/index-23-1182081791667001860.wt
/config/db/index-9-1182081791667001860.wt
/config/db/index-21-1182081791667001860.wt
/config/db/index-22-1182081791667001860.wt
/config/db/index-25-1182081791667001860.wt
/config/db/index-1--4130828054873547616.wt
mono 5966 Kill 4 4 /config/Duplicati-server.sqlite
/config/control_dir_v2/lock_v2
/tmp/dup-d7ed66c6-c728-450f-9dd5-eeb13f6496a4
/tmp/dup-fa712d0c-e1fa-47fc-b064-eec28ea425c5
find 6685 Kill 1 1 /mnt/user/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/ ...
mono 7188 Kill 9 7 /config/logs.db-shm (stat: No such file or directory)
/config/nzbdrone.db-shm (stat: No such file or directory)
/config/logs.db
/config/logs.db-wal
/config/logs.db-shm
/config/nzbdrone.db
/config/nzbdrone.db-wal
/config/nzbdrone.db-shm
/config/logs.db
python 7561 Kill 1 1 /config/logs/headphones.log
Plex Media Serv 8075 Kill 50 48 /config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/ ...
/config/Library/Application Support/Plex Media Server/Cache/gn_lists.gdb
/config/Library/Application Support/Plex Media Server/Logs/Plex Media Server.log
Plex Script Hos 8119 Kill 2 2 /config/Library/Application Support/Plex Media Server/Plug-in Support/Data/com.p ...
/config/Library/Application Support/Plex Media Server/Logs/PMS Plugin Logs/com.p ...
Plex Tuner Serv 8422 Kill 2 2 /config/Library/Application Support/Plex Media Server/Logs/Plex Tuner Service.lo ...
/config/Library/Application Support/Plex Media Server/Logs/Plex Media Server.5.l ...
mono-sgen 8739 Kill 11 9

/config/nzbdrone.db-shm (stat: No such file or directory)
/config/logs.db-shm (stat: No such file or directory)
/config/nzbdrone.db
/config/nzbdrone.db-wal
/config/nzbdrone.db-shm
/config/logs.db
/config/nzbdrone.db
/config/logs.db-shm
/config/logs.db
/config/logs.db-wal
/config/nzbdrone.db-wal
 

see.png

Edited by nuhll

Share this post


Link to post

You're fast... was going to add: the 99.1% you're seeing is the sum of 10 processes - do you have something hammering storage that much?

Share this post


Link to post

Like i said i have 2 cameras running with xeoma docker, but cpu keep beeing high when i stop the docker...

 

Which wrote since 17.01 18gb... to 4 directorys (on cache!)

 

The usuall dockers, but they are not doin much the last days... here and there an automatic update...

Edited by nuhll

Share this post


Link to post

In the logs you posted, there's a python process in a docker container consuming 67% CPU.

Share this post


Link to post

Dont be so cryptic :P 

 

Which docker? Which script?

 

cadvisor doenst show anything usefull for me.

 

 

It also just show this shsf with 70% cpu

 

root 4.050 1 Jan13 70.10 0.40 65.23 MiB 1.40 GiB Ssl 2-23:35:36 shfs /
root 1.979 1.978 02:30 30.80 0.00 1.21 MiB 12.03 MiB R 00:00:03 find /
root 24.563 24.556 02:19 10.70 0.70 119.79 MiB 2.18 GiB Sl 00:01:07 xeoma /docker/4825cce57e348e65242ac4
root 31.208 31.191 02:27 3.60 0.30 56.00 MiB 422.33 MiB Ssl 00:00:05 cadvisor /doc

 

 

Or is it just overall useage from all my dockers?

 

Ah you mean dupeguru? Yeah, the diagnostic creation took long, so i startet dupeguru and deleted some duplicates... this is only running when i use it. 

unraid-server-diagnostics-20180118-0234.zip

 

There u see some load by dir cache plugin, but this is only there because i was using unraid, if i dont use it, all runs on cache so no hdd spin up, so no dir cache is created...


Also, there doesnt seem to be any file reads/writes even the cpu is at 70% oO

Edited by nuhll

Share this post


Link to post

I'm just going to be honest: I don't know what's happening with your particular server.  There isn't a general issue where everyone is seeing high cpu usage in this manner.  It's gong to take time I don't have right now to investigate this case further.

Share this post


Link to post

Ah, okay.

 

Its normal for me most time also, just i guess, after some days without restart.

 

Could it have anything to do with xeoma?

 

Because i get many errors like: 

Jan 18 23:01:24 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-16

 

How to investigate it? This Docker dont have any usefull logs, as it seems. While the high cpu also persists if i close xeoma, it could still be the "WHY" is it happening, or not?!

 

Could you tell me what this "/usr/local/sbin/shfs /mnt/user -disk 1023 204800000 -o noatime,big_writes,allow_other -o remember=0" is? What is it running? Is it from unraid? or is it from linux? Is it mover? Or what? It seems to run all time, if its not bugged it seems like capped at 10% CPU.

 

Edited by nuhll

Share this post


Link to post
1 hour ago, nuhll said:

Could you tell me what this "/usr/local/sbin/shfs /mnt/user -disk 1023 204800000 -o noatime,big_writes,allow_other -o remember=0" is? What is it running? Is it from unraid? or is it from linux? Is it mover? Or what? It seems to run all time, if its not bugged it seems like capped at 10% CPU.

 

It's a FUSE application - a userspace file system.

 

It's the program that reads the directories from the different disks, and creates a merged user share.

 

What you see is the mount command, where the application /usr/local/sbin/shfs mounts itself as a file system named /mnt/user. The rest is parameters how the file system should work.

Share this post


Link to post
2 hours ago, nuhll said:

Ah, okay.

 

Its normal for me most time also, just i guess, after some days without restart.

 

Could it have anything to do with xeoma?

 

Because i get many errors like: 

Jan 18 23:01:24 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-16

 

How to investigate it? This Docker dont have any usefull logs, as it seems. While the high cpu also persists if i close xeoma, it could still be the "WHY" is it happening, or not?!

 

Could you tell me what this "/usr/local/sbin/shfs /mnt/user -disk 1023 204800000 -o noatime,big_writes,allow_other -o remember=0" is? What is it running? Is it from unraid? or is it from linux? Is it mover? Or what? It seems to run all time, if its not bugged it seems like capped at 10% CPU.

 

 

The message can be output by the 'mover' process.  Recall that mover moves files between array and cache.  Share 'Use Cache" setting Yes means files will move from cache to array, setting Prefer means files will move from array to cache.

 

To move files, the mover looks at files on the source and moves them to the target.  After all files from a directory have been moved, it attempts to rremove (delete) the source directory.  If there are still files left in the source directory, the above error is output and the source directory is left in place.

 

How could there still be files left in the source directory if they were supposedly moved to target?  Several things can cause this:

  • The source file was "in use" at time mover wanted to move it.  You see this mostly with loopback-mounted image files, but could happen if a file is opened by some other process.
  • There was an error moving the source file to the target, for example, out of space on target.
  • A file got created in the directory after the mover fetched the directory list.  In this case the file will get moved next time mover runs.

Another time that error can be output is if some process attempts to delete a directory that's not empty.

Share this post


Link to post

But i dont think its the mover, xeoma is now on cache only (that was my first thought). 

 

Besides this, only 1 or 2 files a day gets moved from cache to array... so.

 

Its now running more then a day, without whole time high spike. Its "just" like every minute at 95% cpu. 

 

Is there a way to debug the process, to see what its doing when it uses that much cpu? Like debug log or something?

Edited by nuhll

Share this post


Link to post

Without access to strace, you can't do much more than check if the application consumes mostly user time or if it's system time.

Share this post


Link to post

It seems like it was caused by dir cache plugin. Ive set different directorys and i have much lower cpu before: 0-40%, now 0-10%.

 

I will check if it fixes the shsf issue.

Share this post


Link to post
On 1/19/2018 at 4:38 PM, nuhll said:

It seems like it was caused by dir cache plugin.

I have the same issue on my system. The directories appdata, domains and system are on my cache drive. After excluding those 3 folders from Folder Caching the system load returned to normal.

 

image.png.5ee2b0e3ec0a22cbd2d5cfedf235faa4.png

Additionaly I had adjusted the Maximum interval between folder scans (sec)

 

Please tag this topic with (SOLVED) if this solved your issue.

 

 

Edited by FlorinB

Share this post


Link to post
3 hours ago, FlorinB said:

I have the same issue on my system. The directories appdata, domains and system are on my cache drive. After excluding those 3 folders from Folder Caching the system load returned to normal.

FYI, since you have Folder Caching disabled, no directories are being cached, regardless of the include / exclude settings.

Share this post


Link to post
5 hours ago, Squid said:

since you have Folder Caching disabled

Sorry. I was played earlier with the settings and forgot to enable back the folder caching.

With the folder caching enabled those are the top 5 processes

Quote

root@Tower:~# ps aux | sort -nrk 3,3 | head -n 5
root      8212 19.0  0.0 702528 15508 ?        Ssl  Jun20 339:02 /usr/local/sbin/shfs /mnt/user -disks 255 2048000000 -o noatime,big_writes,allow_other -o remember=0
root      6457  6.2  0.0  11972  2608 ?        SN   11:32  37:25 sh
root      7464  3.6  0.0      0     0 ?        S    Jun20  64:19 [unraidd]
root      6244  2.1  0.0      0     0 ?        S    Jun20  37:27 [mdrecoveryd]
nobody   24372  1.7  0.0 172468 11944 ?        S    10:46  11:04 nginx: worker process
root@Tower:~#
 

Now my CPU load is fluctuating between 15 - 40%, in comparison with 2-5% whithout folder caching enabled. See the highlighted zone.

image.png.de893f60d2848c56f3a53a1a8997799f.png

 

Edited by FlorinB

Share this post


Link to post

... its normal that you get more work to do when you activate something.

 

You shouldnt exclude, remove that, better JUST include what you need to MANUALLY browse. Since i changed it that way i didnt had a single problem with the folder cache for months now. I also didnt changed any other option.

 

I added my archive (movies, mp3s, games) and the download folder. 

Edited by nuhll

Share this post


Link to post

I found this thread having the same problem with this process chewing up 90% cpu in htop:

 

/user/local/sbin/shfs /mnt/user -disks 15 2048000000 -o noatime,allow_other -o remember=0

 

Turns out, it was my one unassigned disk with an NTFS partition mounted and shared.  I only have this issue with my CrashPlanPro docker is running a backup on other drives (no open files on the unassigned disk).

 

Unmounting the drive or stopping the backup job fixes the issue for some reason.

 

Also I didn't have folder caching plugin installed.  Bizarre.

Share this post


Link to post

So I had to rebuild my dockers due to cache pool corruption and now I'm having the same issue, though I don't have any more NTFS drives.  My issue is now my crashplanpro docker service. 

 

Share this post


Link to post
On 6/21/2018 at 9:34 PM, FlorinB said:

Sorry. I was played earlier with the settings and forgot to enable back the folder caching.

With the folder caching enabled those are the top 5 processes

Now my CPU load is fluctuating between 15 - 40%, in comparison with 2-5% whithout folder caching enabled. See the highlighted zone.

image.png.de893f60d2848c56f3a53a1a8997799f.png

 

 

So glad I found this thread. I've observed the exact same behaviour i.e. when I disable the folder caching the CPU spikes vanish. I try to play around with the plugin settings in order to find a trade-off between spikes and having folder caching in place. Will report back.

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.