Re: nbd questions and problems

["Steve Kieu" <haiquy@yahoo.com>]

 --- Paul Clements <paul.clements@steeleye.com> wrote:

>  > It seems fine, but when the system touch swap
> there are error in the
>  > kernel log
>  >
>  > nbd0 Receive control failed result -104
>  >
>  > and the server exited .
> 
> Well, -104 is Connection reset by peer. Nothing in
> nbd would cause that 
> directly. Without seeing the error messages from the
> nbd-server it's 
> hard to tell, but I suspect that either nbd-server
> is dying at startup 

Nope, when I start the server it is running (waiting
for communication. When the client connect it is still
running (it print some thing like begin loop
request..). It only exited to the bash prompt without
any message. The syslog has a message (just found it)

nbd_server[16808]: Request too big!

probably is the reason why the server exited.

> (check the syslog on the server, a common cause is
> failure to open the 
> file/partition) or you have some sort of networking
> issue. Can you 
> otherwise communicate between the two systems over a
> TCP connection ?

I am sure the file is ok ; the communication is ok. As
later I succesfully ran enbd reliably (only with
2.4.27 in client, the 2.6.7 OOPs) so we can confirm
the TCP is good AFAIK enbd uses the same protocol. Can
ssh between the two machine, can http (run web browser
in client and access a page served by the server box
vise versa).

I will do more testing today. I need 2.6.8 kernel in
the client.

Kind regards,



=====
S.KIEU

Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com