Re: General question

In article <[email protected]> you wrote:
> On Sun, 5 Jun 2005 19:28:55 +0200 (MET DST)
> "Peter T. Breuer" <[email protected]> wrote:

> > "Also sprach Stephan von Krawczynski:"
> > > unplugging the network between the two enbd-servers.
> > > Now something interesting happens:
> > > Bonnie stops right away (freezes), the raid1 in fact freezes. You cannot do
> > 
> > You are supposed to use FR1 with enbd, not raid1.

> I did.

OK - well that turns on show_errs when the enbd device is used inside a
raid1 (FR1) device, so I don't know what is going on. I would suspect
that you are NOT using fr1, although you think you are ...

> > > anything with it. You cannot even setraidfaulty the now-gone enbd-server
> > > partition.
> > 
> > It sounds like you are not using enbd with show_errs set (so raid1 sees
> > no error, but simply blocks forever when enbd cannot complete a
> > transaction, since enbd blocks forever waiting for a reconnect).  But
> > anyway, use FR1. Then you don't need to set anything.

> Well, as stated, I did use fr1.  See:

Are you sure that you are using the NEW md module? That's the part that
is responsible for telling the enbd module that it is in a raid array,
and for reacting to a network error message from enbd.

> :~ # lsmod
> Module                  Size  Used by    Not tainted
> fr1                    18356   1 
> bitmap                  6416   0  [fr1]
> md                     49664   2  [fr1]
> enbd                   71788   8 

> Dumb question: how do I set show_errs ?

You don't - it's done for you if you ue the md/fr1 pair from the fr1
patch. But it should be shown in the output of /proc/nbdinfo (State
line).  And you can turn it on manually by echoing show_errs=1 to
/proc/nbdinfo, or by using it as a module parameter.  I think there
might be inputs for it in /proc/sys/dev too, but don't quote me on that!

Peter