Hi,

 

I'm having an issue with a process using high CPU usage 100%. The process is shfs.

 

I've shutdown VMs and most of the dockers but it remains at 100% usage and is constant.

 

I've attached my diagnostics.

 

Thanks.

nasbox2-diagnostics-20230317-0729.zip

8 hours ago, dreamsy said:

I'm having an issue with a process using high CPU usage 100%. The process is shfs.

Just to be clear, that's 100% of one core. Your overall cpu usage doesn't look high

shfs is the merge filesystem used by shares that gives the shares a unified view across all the array and pool drives. If there are lots of writes, it will have overheads. Essentially this is the /mnt/user mount

 

Moving any drive specific writes to /mnt/disk is one way to avoid shfs overhead, though it would bypass the shares so not always desirable

 

You also have some mount related warnings on fix common problems. You should fix those docker containers too

Edited March 17, 20233 yr by apandey

1 hour ago, apandey said:

Just to be clear, that's 100% of one core. Your overall cpu usage doesn't look high

shfs is the merge filesystem used by shares that gives the shares a unified view across all the array and pool drives. If there are lots of writes, it will have overheads. Essentially this is the /mnt/user mount

 

Moving any drive specific writes to /mnt/disk is one way to avoid shfs overhead, though it would bypass the shares so not always desirable

 

You also have some mount related warnings on fix common problems. You should fix those docker containers too

Yes that is 100% of 1 core.  But that is 100% of a single core that I did not have previously. 

Something has changed recently that this happening. I'd like to know what is causing this. 

There is no activity on the box. I've shutdown the VMs and everything else that would talk to it.

 

I've also noticed recently that I have /mnt/user0 folder - folders/files are duplicated between /mnt/user and /mnt/user0.

 

Edit: Just read what /mnt/user0 is.

 

Thanks

 

 

 

Edited March 17, 20233 yr by dreamsy

10 hours ago, dreamsy said:

But that is 100% of a single core that I did not have previously. 

Something has changed recently that this happening

what is previously here? Did you do any updates between this previous and current state? 

 

10 hours ago, dreamsy said:

There is no activity on the box. I've shutdown the VMs and everything else that would talk to it.

Are you sure about this? The diagnostics you posted has a bunch of dockers running, in fact python is taking 1 core too. I see sabznet running, and probably a few other things. docker appdata is under /mnt/user, maybe some other container mounts too? docker and VM services are enabled from your diagnostics. Are clients connected over network too - smb, nfs, ssh?

If things have changed since that diagnostics, post a new one when you have activity stopped

 

Also, as mentioned earlier, fix common problems is showing issues, including incompatible plugins. How have you arrived there? was there an unraid version upgrade involved at some point? better to resolve issues and be up-to-date first in that case 

On 3/18/2023 at 4:31 AM, apandey said:

what is previously here? Did you do any updates between this previous and current state? 

 

Are you sure about this? The diagnostics you posted has a bunch of dockers running, in fact python is taking 1 core too. I see sabznet running, and probably a few other things. docker appdata is under /mnt/user, maybe some other container mounts too? docker and VM services are enabled from your diagnostics. Are clients connected over network too - smb, nfs, ssh?

If things have changed since that diagnostics, post a new one when you have activity stopped

 

Also, as mentioned earlier, fix common problems is showing issues, including incompatible plugins. How have you arrived there? was there an unraid version upgrade involved at some point? better to resolve issues and be up-to-date first in that case 

Not done an update for a while - so not sure exactly when this started.

 

I've fixed the warnings reported in fix common problems. Just have the jumbo frames warnings left which I believe I can ignore.

I've stopped Docker and VM in the settings.

 

All clients are stopped (Except on PC - but I cannot see any activity from it).

 

I've uploaded the latest diagnostics.

 

Thanks.

 

 

 

nasbox2-diagnostics-20230319-1203.zip

I see you have cache dirs plugin. Can you confirm if "scan user shares" is set to yes? That can cause higher CPU usage

I do have this plugin installed (not sure when I installed it) but it is disabled.

 

To answer your question - the  "scan user shares" setting is set to "No".

Any other suggestions please?