I received a notification that SMBD suffered a diaper overflow and dumped core.
Problem/Justification
None
Impact
None
Activity
Show:
Evan Hillman
October 5, 2021 at 9:52 PM
Thank you! An aside - I was able to copy over 40 TB from one pool on the server to the other using FileZilla. FileZilla was running on my desktop. It took days, but there wasn't a single error. Is it likely that would have happened if in fact I have network problems? Also, I am running a low quality and unstable VPN on my desktop (Nord). It does drop out occasionally, and at time I have to shut it down to send an email which also causes my desktop to briefly disconnect from the network. Could that cause what you were seeing in the log?
Looks like crash during server-side copy. Some details aren't clear, but looks like possibly network event and crash during SMB session teardown. Some users have reported more stability by turning off durable handles for their shares in this case. I can improve error handling so that we don't crash, but SMB session stall / encounter issues. If this is happening on a regular basis you may need to investigate hardware / networking.
Andrew Walker
September 23, 2021 at 8:11 PM
Core file isn't attached. Please re-upload.
Evan Hillman
September 23, 2021 at 6:09 PM
(edited)
As far as I can tell I have added the core file. I thought the debug file was uploaded earlier when I created the bug report.
I received a notification that SMBD suffered a diaper overflow and dumped core.