@Lee Tae Hoon, thank you for the feedback. I downloaded the zip file you provided, but I still can't see anything useful in the logs. I wonder what's really happening. I will have to bug you one more time and ask you to provide a network trace of the moment of the failure, please. You can read this guide here:
Specifically the "Testing daemons" and the "Network trace" sections, and follow the instructions from there.
Thanks also for investigating the scenarios where this bug manifests or not. I don't have access to a macbook here, so I wonder what else I can do to reproduce this.
@Rapper_skull, thanks as well for the help. If I understand correctly, you are not using a macbook in your setup, right? Since I don't have access to one, it might be a "good sign" that you don't need a macbook to reproduce it.
I appreciate you verifying that you can't reproduce the bug in a VM. The problem here is that I don't have access to this "affected folder" you mention, and I can't seem to be able to create one.
I will keep trying to reproduce it here, but I'd like to ask if you could follow the same instructions I gave to Lee Tae Hoon and provide (a) your full logs (with debug enabled) of the moment the failure happens, and (b) a network trace.
@Lee Tae Hoon, thank you for the feedback. I downloaded the zip file you provided, but I still can't see anything useful in the logs. I wonder what's really happening. I will have to bug you one more time and ask you to provide a network trace of the moment of the failure, please. You can read this guide here:
https:/ /www.samba. org/~asn/ reporting_ samba_bugs. txt
Specifically the "Testing daemons" and the "Network trace" sections, and follow the instructions from there.
Thanks also for investigating the scenarios where this bug manifests or not. I don't have access to a macbook here, so I wonder what else I can do to reproduce this.
@Rapper_skull, thanks as well for the help. If I understand correctly, you are not using a macbook in your setup, right? Since I don't have access to one, it might be a "good sign" that you don't need a macbook to reproduce it.
I appreciate you verifying that you can't reproduce the bug in a VM. The problem here is that I don't have access to this "affected folder" you mention, and I can't seem to be able to create one.
I will keep trying to reproduce it here, but I'd like to ask if you could follow the same instructions I gave to Lee Tae Hoon and provide (a) your full logs (with debug enabled) of the moment the failure happens, and (b) a network trace.
Thanks.