Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consumed connection cannot be reused after disconnect #126

Open
Gnlfz007 opened this issue Sep 6, 2021 · 1 comment
Open

Consumed connection cannot be reused after disconnect #126

Gnlfz007 opened this issue Sep 6, 2021 · 1 comment

Comments

@Gnlfz007
Copy link

Gnlfz007 commented Sep 6, 2021

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.

[vol-test]
exportname=/dat/nbd-export/vol-test
maxconnections=1

On the client, the following commands result in an unexpected error message:

> sudo nbd-client my_nas -N vol-test /dev/nbd0
Negotiation: ..size = 1024MB
Connected /dev/nbd0
> sudo nbd-client -d /dev/nbd0
> sudo nbd-client my_nas -N vol-test /dev/nbd0
Negotiation: ..Error: Connection not allowed by server policy. Server said: Access denied by server configurationguration for th�
Exiting.

The only cure I know is systemctl restart nbd-server on the server. Is this an expected behavior, or rather a bug?

@Gnlfz007 Gnlfz007 changed the title Consumed connection cannot be resues after disconnect Consumed connection cannot be reused after disconnect Sep 6, 2021
@Gnlfz007
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant