init scripts problems ?

Hi peter,

Good news, my enbd-fr1 servers were working for a long time without any 
problems!

But now, thanks to a power outage with UPS batteries dead, i notice a 
potential problem with init scripts :

I'm exporting two enbd device on the server, and it seems that enbd init 
script is doing something wrong when restarting enbd link  :

Sounds like a race condition between enbd script and 
enbd-sstatd/enbd-cstatd daemons, causing enbd-client to be lauched twice 
nearly at the same time, leaving enbd in an undefined state, nearly 
impossible to recover, except with reboot:(
the same problem occurs when i start the 2 clients simutlaneously with 
init script

If i start server A first, then client A, wait 30 sec, then start server 
B, client B, everything goes fine.

So there are two potential points :

- simultaneous start/stop of different clients
- protection of enbd init script from automatic sstatd/cstatd connexion

I looked a little bit at enbd init script again, and some code seems to 
be redundant or interfered with the sstatd/cstatd mechanism. So, can i 
rely on this script, or it is preferable to use directy enbd-client and 
enbd-server in my redundancy scripts ?



The other point we discuss later was the ability of saving fr1 bitmap 
from user-space when stopping the array, allowing fast reconstruction to 
be relocated on another node. Have you any new ideas about that (like a 
/proc/fr1 file for example)  ?

Denis