Re: fixup_slot failed to find slot....

"Also sprach scunacc:"
> 14 enbd-server processes running on 14 machines.
> 
> I have one client machine.

OK.

> Running 14 enbd-client processes - each connecting with a different
> identifer to each of the 14 server processes.

The client identifier doesn't matter - it only helps distinguish
connections to the SAME server from the SAME client machine, which is
not your case.

> Once I then have the nb devices on the client, I then create a RAID

What "nb devices"? Can you be very specific here please? I'd like to see the
command lines for the first five clients.

> And it *did* all work (for a time - before the time skew issue) on the
> *other* machine that was acting as a client (FC4+2.6.9).

You have to be very sure about this. I am still guessing the device
names are wrong.

> > for enbd. Maybe using the same devices that you would be using for nbd?
> 
> Nope. Taking care on that. I think. Hmmm. Altho... Hmmm Wondering about
> something...
> 
> 
> If the other devices *exist* in /dev for the nbd driver (with the same
> Maj/min numbers) I wonder if something *is* getting confused.

I'm not sure what you mean exactly ... can you show me the command
lines for the 5 first clients? 

> But other than that - no I am not confusing the device names - certainly
> not when I am connecting using nbd-client.

You might be. They are different from the ones used by the kernel nbd
driver. You want to use "nda" and "ndb" where the kernel driver would
use "nd0" and "nd1" (from memory). And present must be also nda1 and
and nda2 etc. and ndb1 and ndb2 etc, for the slave processes.

Peter