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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx> wrote:
>
> On Sat, 22 Aug 2015 22:32:00 -0300 fsateler@xxxxxxxxxx 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?


[1] http://sources.debian.net/src/mdadm/3.4-1/debian/mdadm-raid/


-- 

Saludos,
Felipe Sateler
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux