Re: mdadm: Has init script in runlevel S but no matching service file

[Jes Sorensen <Jes.Sorensen@redhat.com>]

Felipe Sateler <fsateler@debian.org> writes:
> Hello upstream mdadm.
>
> I'm adding you to CC to resolve the issue of an init script that
> current debian uses, that might possibly be redundant. Please see my
> below diagnosis
>
> On 24 December 2015 at 16:10, Felipe Sateler <fsateler@debian.org> wrote:
>>
>> On Sat, 22 Aug 2015 22:32:00 -0300 fsateler@debian.org wrote:
>> > Hi,
>> >
>> > Your package mdadm has an initscript that is enabled in runlevel S,
>> > but it does not provide a corresponding systemd service unit.
>>
>> It seems that the mdadm-raid init script (which triggered this bug
>> report) is not useful on a udev system (which all systemd systems
>> are[1]). The file /lib/udev/rules.d/64-md-raid-assembly.rules assembles
>> the arrays incrementally as devices are known to udev, and so running
>> a separate assembly step should be superfluous. If this is not true,
>> then maybe this should be reported upstream, as there is a systemd
>> service missing.
>
> For reference, the init script in question can be seen in the souces
> site[1]. On boot, it invokes mdadm --assemble and reports some status
> messages for each md device.
>
> So, the questions are: is this init script redundant on a udev system?
> If not, isn't an equivalent systemd unit missing upstream?

I haven't looked at Debian's scripts here, but whatever Debian uses as
init scripts to control mdadm startup is decided by the Debian mdadm
maintainer. We do carry a set of system files for mdadm in the
mdadm/systemd directory, so if something is missing, it may be that the
Debian maintainer forgot to include it.

Jes