Re: Possible bug in multipathd (getting a segfault)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* 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.

Regards
-- 
Tore Anderson

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux