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

nbd-client fails to allow "-d" disconnect after server disconnect #94

Open
tomjridge opened this issue Jan 20, 2019 · 3 comments
Open

Comments

@tomjridge
Copy link

After a server crash, I restart and try to reconnect with nbd-client:

$ ~ $ sudo nbd-client localhost /dev/nbd0
Warning: the oldstyle protocol is no longer supported.
This method now uses the newstyle protocol with a default export
Negotiation: ..size = 1024MB
bs=1024, sz=1073741824 bytes
Error: Kernel doesn't support multiple connections

Exiting.

I read the man page, and try various things:

$ ~ $ sudo nbd-client -d /dev/nbd0
disconnect, sock, done

However, I still get the "multiple connections" error. And if I try to disconnect again, I get disconnect, sock, done again (and again and again).

I also try:

$ ~ $ sudo nbd-client -c /dev/nbd0
11357

So it looks like the kernel thinks that nbd0 is still connected.

@tomjridge
Copy link
Author

This is with an nbdkit server.

@yoe
Copy link
Member

yoe commented Jan 21, 2019

@josefbacik

@tomjridge
Copy link
Author

Another thing: after the server crash, something on the client "segfaults". Presumably something to do with the nbd-client that was running.

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

2 participants