[dm-devel] RH init.d/multipathd refuses stop
Oren Held
oren at held.org.il
Sun Sep 27 09:49:02 UTC 2009
Hello,
On July 2008, a patch was added to multipathd init script that prevents the
'stop' action if the root device is multipathed. It is described in BZ
#456228. The patch is redhat-only, and isn't found in the upstream git.
I believe that as a general rule, we should let the sysadmin stop/restart her
system services, in all cases that do not pose risk to the system. AFAIK,
stopping multipathd does not pose risk in most cases, even when root is
multipathed.
I've found myself needing to restart/stop multipathd on some cases, be it to
fix a problem which reload didn't fix (i.e. remap everything from scratch) or
put multipathed in debug mode, and not doing it through the init script
doesn't seem right.
Can anybody shed light on the reason why it is dangerous to allow the sysadmin
to manually restart or stop the service?
Is it iSCSI-only? should we really prevent stop also on the more common,
FC/SATA cases?
Thanks,
Oren Held
More information about the dm-devel
mailing list