[ENBD] Client freeze with Reiserfs over enbd

[Peter T. Breuer]

Let me just see if I can squeeze something more out of this data.
Daemon.log may contain more.

"Brian Keefer wrote:"
> > May 11 22:51:07 moya enbd-client: enbd-client: client (1) found device /dev/nda2 ok 
> > May 11 22:51:07 moya enbd-client: enbd-client: client (1) opened socket 5 to 192.168.1.9:2010 
> > May 11 22:51:07 moya enbd-client: enbd-client: client (1) read passwd ok from 192.168.1.9:2010 
> > May 11 22:51:07 moya enbd-client: enbd-client: client (1) got cliserv magic ok from 192.168.1.9:2010 
> > May 11 22:51:07 moya enbd-client: enbd-client: client (1) got a signature ok from 192.168.1.9:2010 
> > May 11 22:51:07 moya enbd-client: enbd-client: client (1) begins main loop 

That must be the tail of a log showing the opening of two slots/channels.

> > May 11 23:07:33 moya kernel: ENBD enbd.c #1691[2]: nbd_rollback rollback req d9413d20, type 1, sector 8581968, 4 blks, 8  sectors from slot 0! 

Now this request was slow in being handled on slot 0. It got retracted
and put on slot 1.

> > May 11 23:07:46 moya kernel: ENBD enbd.c #1691[3]: nbd_rollback rollback req d9413d20, type 1, sector 8581968, 4 blks, 8  sectors from slot 1! 

... where it was also slow, and it got retracted from there too. I don't
know where it went next. Back to 0 in theory.

> > May 11 23:07:53 moya kernel: ENBD enbd.c #2410[0]: nbd_ack ignoring ack of req d9413d20 which slot does not have 

Anyway, a reply eventually came in on slot 1, but not on slot 0. Way late.
It missed on slot 1. Maybe on slot 0 it hit. Or maybe this is a
horrible race condition ... 

> > May 11 23:11:17 moya syslogd 1.3-3: restart.

I'm going to strip the internal raid implementation out.  That may
remove some of the bugs that were introduced with the experiment.  I
already prepared a 2.4.32 directory.

Peter