On Thu, 16 Jun 2016 15:28:42 +0530 Ritesh Raj Sarraf <r...@debian.org> wrote:
> On Wed, 2016-06-15 at 14:05 -0600, Andrew Patterson wrote:
> > The systemd multpath-tools.service loads multipath modules using the
> > following
> > line:
> >
> > ExecStartPre=/sbin/modprobe -a scsi_dh_alua scsi_dh_emc scsi_dh_rdac dm-
> > multipath
> >
> > While the sysvinit file /etc/init.d/multipath-tools-boot loads modules with:
> >
> > modprobe dm-multipath 2> /dev/null || true
> >
> > The /usr/share/initramfs-tools/scripts/local-top/multipath load modules
> > using:
> >
> > MP_MODULES="dm-multipath dm-emc"
> > for module in ${MP_MODULES}; do
> > Â if modprobe "$module"; then
> > Â Â Â verbose && log_success_msg "loaded module ${module}."
> > Â else
> > Â Â Â log_failure_msg "failed to load module ${module}."
> > Â fi
> > done
> >
> > All three of these methods should load the same set of modules (the
> > systemd one seems to be best). Perhaps, there should be a
> > /etc/default/multipath-tools config file that governs which modules to
> > load?
>
> Yes. That'd be good. Perhaps the module loading could be delegated to a
> separate
> shell script. Such a script can then be invoked in ExecStartPre for systemd,
> and
> for shell initscripts we'll just have to source it into the main initscript.
Yes. Although it may take some work to get it into the initramfs.
>
> Do you want to submit a patch for this ?
>
>
I would be happy too. Give me a couple of days.
--
Andrew Patterson
Hewlett-Packard Enterprise
