Red Hat Bugzilla – Bug 196916
Multipath needs to interact with gnbd better
Last modified: 2010-01-11 21:26:20 EST
There are two issues where multipath doesn't deal with gnbd devices well.
1. If multipathd is started before the gnbd module is loaded, multipathd starts
monitoring all 128 possible gnbd devices. This get's rather annoying.
Currently, the workaround for this is to either start or restart multipathd
after the gnbd modules are loaded. The other possibility is to add the following
multipathd should never monitor gnbd devices that aren't activated.
2. The default getuid callout for GNBD devices is "/sbin/gnbd_import -U
/block/%n". Unfortunately, with this callout, if there are any warning messages
printed while running the command, they will end up as part of the UID. This
keeps the maps for correctly being set up. The default getuid needs to be
"/sbin/gnbd_import -q -U /block/%n". As a workaround, people using gnbd can put
the following in the /etc/multipath.conf:
getuid_callout "/sbin/gnbd_import -p -U /block/%n"
Created attachment 134728 [details]
patch for multipath.dev, so that multipath only monitors the correct devices
This patch fixes the first problem, where multipathd monitors unused gnbd
devices. Even with this patch, it is still necessary to modify the
multipath.conf file as described
Added these fixes to the multipath package
Just to note, to apply the multipath_gnbd_update.patch from Comment #1
# patch -p0 -d /etc/dev.d/block/ < multipath_gnbd_update.patch
This fix is in the latest snapshot. Please retest with the latest packages:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.