You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having problems using the path mounts and also when trying to implement similar functionality via the go-nbd library.
When using NewDirectPathMount in a loop, the server sometimes ends with EOF error, while the client returns device or resource busy and fails to connect.
You should be able to use the following snippet to replicate the behavior:
I'm having problems using the path mounts and also when trying to implement similar functionality via the
go-nbd
library.When using
NewDirectPathMount
in a loop, the server sometimes ends withEOF
error, while the client returnsdevice or resource busy
and fails to connect.You should be able to use the following snippet to replicate the behavior:
Here are logs from a run showing the error:
The
Failed to handle server: EOF
is from the log I added here.When I change how the NBD devices are acquired so it is not just one being reused, the problem is still there.
When digging deeper, the problem seems to be somewhere during the transmission (https://github.com/pojntfx/go-nbd/blob/main/pkg/server/nbd.go#L332). Do you have any ideas or insights into why this is happening? Do you think this could be some problem with the host setup?
This was tested on
Ubuntu 22.04.4 LTS
with kernel6.5.0-1025-gcp
and 4096 created NBD devices.Also, thank you for creating this library,
go-nbd
, and writing the thesis.The text was updated successfully, but these errors were encountered: