[dm-devel] Possible bug in multipathd (getting a segfault)
S. J. van Harmelen
svh at dds.nl
Tue Nov 20 11:25:50 UTC 2007
On Tue, 2007-11-20 at 12:15 +0100, Tore Anderson wrote:
> * S. J. van Harmelen
>
> > I guess I don't have to do that as I compiled the multipath-tools
> > myself?
>
> Then you should have the debugging symbols in place, yes.
>
> > I did compile them when running the 2.6.22.2 kernel though. Should I
> > recompile them when running the 2.6.23.1 kernel, or doesn't that
> > matter?
>
> Doesn't matter.
>
> > Oke, the segfault happens right at the start (and only at the start),
> > so that shouldn't be a problem. But I have to stop the running
> > mulipathd and that seems like a problem. This machine is running in
> > production :)
> >
> > So that will have to wait until I get a maintance window I guess...
>
> Stopping multipathd isn't problematic. It is only responsible for
> periodically testing paths to pre-emptively fail non-active paths or
> re-instate paths that has been failed by the kernel's dm-multipath layer.
>
> If everything is running stable with all paths alive and well,
> restarting multipathd is nothing to worry about.
Oke, then I will give this a try this evening and post the results here
for de developers...
Thanks!
>
> Regards
More information about the dm-devel
mailing list