]> git.ipfire.org Git - thirdparty/mdadm.git/commit
mdmon@.service: Change type of process start-up to 'forking'.
authorPawel Baldysiak <pawel.baldysiak@intel.com>
Thu, 6 Mar 2014 14:51:44 +0000 (15:51 +0100)
committerNeilBrown <neilb@suse.de>
Tue, 11 Mar 2014 03:42:57 +0000 (14:42 +1100)
commit2167de78aab599e7a7a8d057ef04bf18527bc129
treeca7c0c69e28031988e34ceb0d47d971599a24af5
parent56bbc588f7f0f3bdd3ec23f02109b427c1d3b8f1
mdmon@.service: Change type of process start-up to 'forking'.

Mdadm does not wait enough time when mdmon is started by systemd.
It causes various problems with behaviour of a RAID volume with external metadata.
For example: mdmon does not update a value of checkpoint during migration
and second RAID5 volume is read-only after reboot done during
container reshape (both problems occur with IMSM matadata).
If a type of process start-up is changed to 'forking', systemctl will
wait until mdmon (parent) process exits after calling fork.
This way mdmon will always be fully initialized after start_mdmon
and these problems will not occur.
In this case it is recommended to add a path to PIDFile, so that systemd
does not have to guess a PID of the mdmon process.

Signed-off-by: Pawel Baldysiak <pawel.baldysiak@intel.com>
Reviewed-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Reviewed-by: Lukasz Dorau <lukasz.dorau@intel.com>
Signed-off-by: NeilBrown <neilb@suse.de>
systemd/mdmon@.service