On Thu, 2009-02-26 at 09:40 +0000, Bryn M. Reeves wrote: > John A. Sullivan III wrote: > > Hello, all. I am running on kernel 2.6.27 on CentOS 5.2 with > > VServer and device-mapper-multipath-0.4.7-17.el5. I have a custom > > mpath_prio_ssi script which takes the device name (e.g., sdaa), > > pulls out the path from /etc/disk/by-path and then echos a priority > > based upon a lookup table. It works perfectly fine from the > > command line. multipath -ll shows the priorities assigned perfectly > > and exactly the right paths are active. > > > > However, when I start multipathd, it all goes down the tubes. The > > paths disappear and /var/log/messages is filled with: Feb 25 > > 20:50:17 vd01 multipathd: error calling out > > /usr/local/sbin/mpath_prio_ssi sdh Feb 25 20:50:17 vd01 multipathd: > > error calling out /usr/local/sbin/mpath_prio_ssi sdi Feb 25 > > 20:50:17 vd01 multipathd: error calling out > > /usr/local/sbin/mpath_prio_ssi sdj Feb 25 20:50:17 vd01 multipathd: > > error calling out /usr/local/sbin/mpath_prio_ssi sdc > > I think you'll need to modify the multipathd binary to achieve this. > > To avoid deadlocking when file system access is interrupted due to > path failures multipathd forks into a new namespace and discards all > the device-backed file systems that are mounted. > > It creates an in-memory file system (ramfs) and copies all the > binaries it will need into this. The file system is locked into memory > so that multipathd can continue to function even if the paths backing > the root file system have all failed. > > For the callouts themselves (getuid and getprio binaries) the config > file processing takes care of this but this only works for stand-alone > binaries. If your script has other dependencies then you'll have to > add code to pull those into the ramfs volume. > > See libmultipath/config.c:push_callout(), > libmultipath/config.c:store_hwe(), > multipathd/main.c:prepare_namespace() and other code that manipulates > the list of binaries stored in conf->binvec. <snip> You were exactly right (of course!). I changed prio_callout from directly calling a bash scrip to /bin/bash scriptname %n and that eliminated the callout errors. However, as expected, the internal calls to bin/ls, bin/grep, etc. all failed. I then rewrote the script to use nothing but bash internals (took a little doing such as getting the path list from /dev/disk/by-path but it seems to work). That, in our initial testing of simply pulling the network cable (no live data transfer yet), multipathd fails the devices and fails them back on recovery but, after recover, all the paths are shown as enabled - none are active. We hope to start live data testing tomorrow. Thanks again - John -- John A. Sullivan III Open Source Development Corporation +1 207-985-7880 jsullivan@xxxxxxxxxxxxxxxxxxx http://www.spiritualoutreach.com Making Christianity intelligible to secular society -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
