network errors

>> Is there any option to make the ENBD client less sensitive to network
>> errors? I am using the -e option, but I don't want to pass temporary
>> network failures (like a small period of high network trafic) to the RAID
>> driver.

>If you are using FR1 instead of raid1, it retries read errors, and
>resyncs the disk intelligently and rapidly if necessary.

I can't use FR1, my ENBD client also has root raid, so to use the FR1 I
have to patch the kernel or boot with a initrd. And this is a production
system, I don't know how much stable is the FR1 patch....
In this system, we have two raid level 5 over the network (each one with 5
machines) and a raid level 0 to agregate this two raids (i.e. it is a raid
0 over raid 5). I am using the -e option because I want the raid driver to
be noticed of serious failures in the machines (like hard disk failures).


>> I think that using the -p option to grow the default heartbeat
>> pulse interval makes the client less sensitive to this kind of erros,
am >> I right?

>Hmm. Depends on the kind of error! If show_errs is not set, then errors
>such as network timeouts will always be retried in the enbd driver and
>never passed on to raid.

>If you like I can add a count to limit the number of retries.

Yes, I think this will solve the problem. Whithout show_errs, the system
will be less sensitive to temporary errors, but with a limitation in the
number of retries it will eventualy show errors caused by more serious
failures. Can you add this as an option to enbd-client?

Rafael