On Thu, Mar 02, 2006 at 11:28:04AM -0500, egoggin@xxxxxxx wrote: > On Thu, Mar 02, 2006 at 12:09:31PM +0100, Christophe Varoqui wrote: > > > On Fri, Feb 24, 2006 at 08:33:29PM -0600, Benjamin Marzinski wrote: > > > > The way multipathd currently works, if you add a map that > > isn't known to > > > > device mapper from multipathd, the first time you run the > > command, it won't > > > > add the map to the mpvec vector. With the attached > > patch, multipathd will > > > > initialize the map and add it to the mpvec vector. > > > > > > > How does the current behaviour affects you ? > > > Is this about races between DM and netlink events ? > > > > > To be more specific, I think the current code rely on the > > netlink "map add" event triggered by coalesce_paths() to feed > > the mpvec asynchronously. > > > > ... which seems ok to me, but I may miss a point. > > What is the "current" code, the code in the git repository or > the latest release point multipath-tools-0.4.6.1? This certainly > works fine in the code from the git repository. > I was refering to the git HEAD. Regards, cvaroqui -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
