[ENBD] fixup_slot failed to find slot....
Peter T. Breuer
ptb at inv.it.uc3m.es
Thu Mar 9 23:43:05 MST 2006
"Also sprach scunacc:"
> > So if you get a segfault, it's not associated with the log message.
>=20
> OK.
The segfault is the problem. No code may segfault. If it does,
something is badly wrong.
> But I do indeed get a segfault and those remaining connections are not
Run a simple test - just one process. Something like
enbd-maketest -n 1 -x /tmp/core --notest --noreload
(one server, one client).
> properly made.
What "remaining connections"? If those are different clients running
on the same driver, then the kernel has oopsed, since there is no
other connection between them.
> A couple of the processes end up as zombies, the rest
> would hang if I tried to work with the devices they are connecting.
A device that is not connected is not working and can tell anyone who
tries to talk to it that it is ill. Are you maybe running in a sync
mode? Maybe you want "-e"
-e This option specifies that the ENBD device will transmit network
errors almost immediately to any higher level device, such as RAID,
that may want to be notified of them. The flag is normally absent
and the ENBD device will hide network errors inter=AD nally, blocking
new requests until they can be me
Peter
More information about the ENBD
mailing list