Re: Re: General question

On Mon, 6 Jun 2005 11:52:25 +0200
[email protected] (Peter T. Breuer) wrote:

> Stephan von Krawczynski <[email protected]> wrote:
> > > 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 
> 
> > It wouldn't open fr1 module if it were the wrong version of md, not?
> 
> It would load and run fine either way, as far as I know. The change to
> md is to allow the hotrepair ioctl/technique plus a notification
> mechanism (again ioctl) for device error.

I checked the sources and the modules. It _is_ the correct module. For testing
I even compiled in some debug messages. It is really the correct, patched md
module.
And the fr1 module does correctly sync by bitmap, btw, as my logs show.
 
> > > > 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!
> 
> > Ok, I set show_err=1 via proc and see the following:
> 
> But it's still not right. It should happen autmatically. I suspect the
> md module is the old one, not the new one.

Can you please point to the source where it does this? Maybe the fr1 patch I
used does not? 

-- 
Regards,
Stephan