[ENBD] enbd on vmware

Simon Edwards enbd@lists.community.tummy.com
Sun, 9 Feb 2003 21:16:27 -0000


Peter,
	Thanks for the quick response. 

	I've attempted a basic test on "localhost" - this time the last
line included is the "main loop" line as shown below.

	The output below shows attempting to serve "/dev/app01vg/test",
checking the server is running. Afterwards I manually insert the modules
and then start the client.

	I'll attempt some more tests, including using nbd rather and
enbd and let you know what happens.

Regards,

Simon.	

root@servera:~# enbd-server 1099 /dev/app01vg/test
file   350<# 418>: rootstatblkdev Warning, could not query
/dev/app01vg/test with BLKROGET: Invalid argument
file   350<# 419>: rootstatblkdev Warning, assuming /dev/app01vg/test is
readwrite:
root@servera:~# enbd-server   351: server (-2) locked
/var/state/nbd/server-6jb69E.client_ips
enbd-server   351: server (-2) unlocked
/var/state/nbd/server-6jb69E.client_ips
enbd-server   351: server (-2) set new signal handlers for master server
351

root@servera:~# ps -fp 351
UID        PID  PPID  C STIME TTY          TIME CMD
root       351     1  0 13:04 pts/0    00:00:00 enbd-server 1099
/dev/app01vg/test

root@servera:~# insmod /lib/modules/2.4.18/kernel/drivers/block/enbd.o
root@servera:~# insmod
/lib/modules/2.4.18/kernel/drivers/block/enbd_bufferwr.o
root@servera:~# insmod
/lib/modules/2.4.18/kernel/drivers/block/enbd_ioctl.o   
root@servera:~# ls -l /dev/nda
brw-r--r--    1 root     root      43,   0 Feb  8 17:15 /dev/nda
root@servera:~# enbd-client localhost:1099 -n 4 /dev/nda
enbd-client   361: client (-1) manager opened NBD device /dev/nda (2b00)
enbd-client   361: client (-1) set kernel bdflush sync boundary to 80%
from 60%
enbd-client   361: client (-1) set kernel bdflush async boundary to 25%
from 40%
root@servera:~# enbd-client   362: client (-1) starts introduction
sequence on port 1099
enbd-server   351: server (-2) opened port 1099 (socket 3) for client
127.0.0.1
enbd-server   363: server (-1) set default signal handlers for session
server 363
enbd-server   363: server (-1) sent passwd ok
enbd-server   363: server (-1) got cliserv magic ok
enbd-server   363: server (-1) received id device 2b00 ok
enbd-server   363: server (-1) sent size 20971520 ok
enbd-server   363: server (-1) sent sig ok
enbd-server   363: server (-1) suggested ro flags 0 ok
enbd-client   362: client (-1) got size 20971520
enbd-server   363: server (-1) received blksize 1024 ok
enbd-server   363: server (-1) sent/negotiated blksize 1024 ok
enbd-client   362: client (-1) negotiated blksize 1024
enbd-server   363: server (-1) received pulse_intvl 10 ok
enbd-server   363: server (-1) sent/negotiated pulse interval 10 ok
enbd-client   362: client (-1) negotiated pulse_intvl 10
enbd-server   363: server (-1) agreed 4 channels ok
enbd-server   363: server (-1) selected free port at 1100
enbd-server   363: server (-1) posted port 1100 ok
enbd-server   363: server (-1) manager started new process group 363
enbd-server   364: server (0) set default signal handlers for slave
server 364
enbd-server   366: server (2) set default signal handlers for slave
server 366
enbd-server   365: server (1) set default signal handlers for slave
server 365
enbd-server   367: server (3) set default signal handlers for slave
server 367
enbd-server   363: server (-1) set new signal handlers for session
server 363
root@servera:~# enbd-client   362: client (-1) got session port 1100 ok
enbd-client   362: client (-1) introduction sequence ends ok
enbd-client   362: client (-1) set device size 20971520
enbd-client   362: client (-1) sets session slots to 0-3
enbd-client   368: client (0) found device /dev/nda1 ok
enbd-server   364: server (0) opened port 1100 (socket 10) for client
127.0.0.1
enbd-server   364: server (0) set new signal handlers for slave server
364
enbd-client   368: client (0) opened socket 5 to port 1100
enbd-client   368: client (0) read passwd ok from port 1100
enbd-client   368: client (0) got cliserv magic ok from port 1100
enbd-client   368: client (0) got a signature ok from port 1100
enbd-client   368: client (0) begins main loop



-----Original Message-----
From: enbd-admin@lists.community.tummy.com
[mailto:enbd-admin@lists.community.tummy.com] On Behalf Of Peter T.
Breuer
Sent: 09 February 2003 20:43
To: enbd@lists.community.tummy.com
Subject: Re: [ENBD] enbd on vmware

"A month of sundays ago Simon Edwards wrote:"
> 	I've successfully compiled and inserted the enbd module (version
> 2.4.30) into the kernel manually, but the "make test" gets as far as
the
> main loop and then hangs (output below) - apparently in a busy loop.

What's the evidence for the loop? The code below never finished the
initial handshake. You'd have to strace something to show a loop ...

> server 278
> enbd-client   275: client (-1) got session port 3034 ok
> enbd-client   275: client (-1) introduction sequence ends ok
> enbd-client   275: client (-1) set device size 8388608
> enbd-client   275: client (-1) sets session slots to 0-3
> enbd-client   284: client (0) found device /dev/ndb1 ok
> enbd-server   280: server (0) opened port 3034 (socket 4) for client
> 127.0.0.1
> enbd-client   284: client (0) opened socket 5 to port 3034
> enbd-client   284: client (0) read passwd ok from port 3034
> enbd-client   284: client (0) got cliserv magic ok from port 3034
> enbd-client   284: client (0) got a signature ok from port 3034
> enbd-client   284:

If you get a hang half way through a syslog/stderr output line,
something
is wrong!  But not in enbd.

You shoudl run with more channels, anyway. There's no point in only one
(it's like running a bicycle with one wheel).


Peter
_______________________________________________
ENBD mailing list
ENBD@lists.community.tummy.com
http://lists.community.tummy.com/mailman/listinfo/enbd