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
On my NAS (Ubuntu-20.04), I defined a volume with option "maxconnections=1, as a workaround for exclusive volume export. This way I want to ensure that my Laptop and my PC do not corrupt a LUKS/ext4 volume accidentally via concurrent mount.
I'm still on Ubuntu 20.04 / kernel 5.4.0-146-generic #163-Ubuntu SMP and the issue persists.
Each connection is consumed forever, even if the client disconnects orderly (-disconnect). Is this actually the expected behavior?
Any new related to this issue?
On my NAS (Ubuntu-20.04), I defined a volume with option "maxconnections=1, as a workaround for exclusive volume export. This way I want to ensure that my Laptop and my PC do not corrupt a LUKS/ext4 volume accidentally via concurrent mount.
On the client, the following commands result in an unexpected error message:
The only cure I know is
systemctl restart nbd-server
on the server. Is this an expected behavior, or rather a bug?The text was updated successfully, but these errors were encountered: