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. > > Regards, > Bryn. <snip> Thank you very much, Bryn. That finally makes sense of it all. Unfortunately, I am not a developer at all and hence approach this more as a systems designer. If I understand you correctly, the best approach would be to create my script as a compiled binary rather than a bash script. Then the config file processing will load it into memory. Is that correct? Does that also imply that the file referenced as the list of iSCSI ids and priorities needs to be embedded in the binary? Is that a non-issue if I am not using multipathing for the devices containing the referenced script? As my skills are limited for converting this from bash to C, could I achieve the same thing by calling bash rather than the script and passing the script as an argument, e.g., prio_callout "/bin/bash /usr/local/sbin/mpath_prio_ssi %n" 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
