Greeting!

I've been using NBD since 2.9.11 and appreciate the functionality and 
simplicity. It's become essential element for software RAID between 
primary and secondary servers for me.

I just tried the named exports function with 2.9.17 and cannot get it 
to work properly. The server that runs the nbd-server is on kernel 
2.6.33.4 arch x86_64 and the server that runs the nbd-client is on the 
same kernel 2.6.33.4 but arch i686.

The nbd-server appears to start up fine using the 
/etc/nbd-server/config file and is listening on the new IANA port 10809 
for connections. When I issue the nbd-client command using the named 
export option I get a screen error and nbd-client syslog error:

Aug 6 12:52:02 x86_64_srv_name nbd_client[5422]: Not enough opts_magic
Aug 6 12:52:02 x86_64_srv_name nbd_client[5422]: Exiting.

This nbd-client error has the nasty side effect of immediately taking 
down the nbd-server too. From the nbd-server syslog:

Aug  6 12:52:11 other_srv_name nbd_server[27812]: negotiation failed
Aug  6 12:52:11 other_srv_name nbd_server[27812]: Exiting.
Aug  6 12:52:11 other_srv_name nbd_server[27812]: fcntl F_GETFL
Aug  6 12:52:11 other_srv_name nbd_server[27812]: Exiting.

I can get nbd-server to work using the oldstyle=true entry and assign 
different ports to each named export in the /etc/nbd-server/config 
file.  I then use the deprecated nbd-client command that includes the 
port but not the named export.

Any ideas?

Chuck


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Nbd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nbd-general

Reply via email to