wsdd 100% using 1 core


scubieman

Recommended Posts

  • 3 weeks later...

@limetechthis issue is open since November 2019, I suffer it from over a year (my report here 

https://forums.unraid.net/bug-reports/stable-releases/683-wsdd-process-at-100-r1123

I know your saying that no response does not mean the issue is not looked at, but this a year and a half. I have also suggested something which may be related in my post, is it ever going to be looked at?
Thanks.
btw (-i br0 does not solve it for me, two machines suffer from the same issue)

Link to comment
  • 2 weeks later...
On 4/24/2021 at 3:18 PM, thecode said:

@limetechthis issue is open since November 2019, I suffer it from over a year (my report here 


https://forums.unraid.net/bug-reports/stable-releases/683-wsdd-process-at-100-r1123

I know your saying that no response does not mean the issue is not looked at, but this a year and a half. I have also suggested something which may be related in my post, is it ever going to be looked at?
Thanks.
btw (-i br0 does not solve it for me, two machines suffer from the same issue)

 

Also had this issue on my otherwise fantastic 6.9.2 server. Added workaround. Will report back.

Link to comment
  • 4 weeks later...

Same here tonight for the first time as far as i'm aware. Asolutely nothing running, system standing idle for days, disks spun down. just dipped in to have a look, see alls ok and one cpu pegged at 100% by wsdd process.  Switched of in settings and it's aok again. No idea what harm that has done, if any? If i mount a local to remote share time to time will this be affected?

Link to comment
  • 2 months later...

I faced this issue for the first time today, and it was solved by just restarting the Docker from Settings menu

 

I shall try using 

-i br0

in WSD Options under SMB settings.

 

I am running docker on VLAN br0.150, so not very sure if that will work. I shall report back once I get the issue solved.

Link to comment
3 hours ago, samba_69 said:

I faced this issue for the first time today, and it was solved by just restarting the Docker from Settings menu

 

Thanks, this resolved it for me as well and is preferred over a reboot. I only had one container running (sabnzb) and now I have none (but docker is active), so I'm curious if it'll happen again under these conditions.

Edited by nate1749
Link to comment
  • 1 month later...

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.