Re: problem with enbd init on standby

Peter T. Breuer wrote:
>One thing I'm confused by ...
>
>  
>>enbd-client 12195: <#2409> expect result from looking for write command bksz is 4
>>enbd-client 12195: <#2427> expect writing data for command bksz
>>enbd-client 12195: <#2434> expect client (-1) suggested bksz 1024 to server
>>enbd-client 12195: <#2437> expect have 0 after offset 4, need 5 more in buf
>>enbd-client 12195: <#2366> fill Warning - read only 0/1B on descriptor 5: Invalid argument
>>    
>
>...  is DO you have -DDEBUG defined during the compile or not?  That
>"expect" output looks like debugging, but there is some stuff missing
>from a debug trace:
>
>       DEBUG ("Fetch %d more bytes from net to total %d\n",
>                          size, tot + size);
>       ...
>       if (count < size) {
>               PERR ("Warning - read only %d/%dB on descriptor %d: %m\n",
>                        count, size, stream->sock);
>       }
>       return count;
>
>and I see the PERR output, but not the DEBUG output. Yet, the expect
>stuff is indeed debugging output:
>
>      DEBUG ("writing data for command %s\n", name);
>
>Perhaps you turned on debugging in the expect() function alone? Maybe you
>could do it in fill() as well.
>
>Peter
>_______________________________________________
>ENBD mailing list
>[email protected]
>http://lists.community.tummy.com/mailman/listinfo/enbd
>  
Ok I only recompiled the client module. Will do the rest tommorow morning!
Thanks so far
Uwe