Bug#514923: mdadm: Inconsistent rc.d links after upgrades and with insserv

Wed Feb 11 22:10:01 UTC 2009

Package: mdadm
Version: 2.6.7.2-1
Severity: normal

Today I upgraded mdadm to the current version in testing and noticed the
following messages:

  Setting up mdadm (2.6.7.2-1) ...
  update-initramfs: deferring update (trigger activated)
  insserv: warning: current start runlevel(s) (2 3 4 5) of script `mdadm' overwrites defaults (S).
  insserv: warning: current stop runlevel(s) (0 1 6) of script `mdadm' overwrites defaults (0 6).
  Starting MD monitoring service: mdadm --monitor.
  Generating udev events for MD arrays...done.

I wondered about these insserv warnings and looked at the rc.d links to see if
everything is fine. Looking at these I noticed that since I activated insserv
the start and kill links look much different than before.

I'm not sure about the severity of this bug, maybe it is just a cosmetic
issue, maybe this can cause some real problems, therefore I collected some
data about my installation for this bug report. Please decide for yourself:

My upgrade history for mdadm and install date for insserv:

  20080331 mdadm 2.6.4-1 (initial installation)
  20080428 mdadm 2.6.4-2
  20080729 mdadm 2.6.7-3
  20080907 mdadm 2.6.7-3.1
  20081101 mdadm 2.6.7.1-1
  20090131 insserv 1.12.0-4 (initial installation and activation)
  20090211 mdadm 2.6.7.2-1

rc.d links before installing (and activating) insserv:

  $ tar tvzf /var/lib/insserv/bootscripts-20090131T1422.tar.gz|grep '[KS]..mdadm'
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc0.d/K25mdadm -> ../init.d/mdadm
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc0.d/S60mdadm-raid -> ../init.d/mdadm-raid
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc1.d/K25mdadm -> ../init.d/mdadm
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc2.d/S25mdadm -> ../init.d/mdadm
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc3.d/S25mdadm -> ../init.d/mdadm
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc4.d/S25mdadm -> ../init.d/mdadm
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc5.d/S25mdadm -> ../init.d/mdadm
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc6.d/K25mdadm -> ../init.d/mdadm
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rc6.d/S60mdadm-raid -> ../init.d/mdadm-raid
  lrwxrwxrwx root/root         0 2008-03-31 18:38 rcS.d/S25mdadm-raid -> ../init.d/mdadm-raid

rc.d links right after today's upgrade:

  $ ls -l rc?.d/???mdadm*
  lrwxrwxrwx 1 root root 20 2009-01-31 14:23 rc0.d/K01mdadm-raid -> ../init.d/mdadm-raid*
  lrwxrwxrwx 1 root root 15 2009-01-31 14:23 rc0.d/K02mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 15 2009-01-31 14:23 rc1.d/K02mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 15 2009-01-31 14:23 rc2.d/S01mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 15 2009-01-31 14:23 rc3.d/S01mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 15 2009-01-31 14:23 rc4.d/S01mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 15 2009-01-31 14:23 rc5.d/S01mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 20 2009-01-31 14:23 rc6.d/K01mdadm-raid -> ../init.d/mdadm-raid*
  lrwxrwxrwx 1 root root 15 2009-01-31 14:23 rc6.d/K02mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 20 2009-01-31 14:23 rcS.d/S07mdadm-raid -> ../init.d/mdadm-raid*

/var/lib/dpkg/info/mdadm.postinst contains:

  update-rc.d mdadm-raid start 25 S . start 60 0 6 .
  update-rc.d mdadm defaults 25

/etc/init.d/mdadm contains:

  # Required-Start:    checkroot
  # Required-Stop:     umountroot
  # Should-Start:      module-init-tools
  # Default-Start:     S
  # Default-Stop:      0 6

/etc/init.d/mdadm-raid contains:

  # Required-Start:    mountkernfs
  # Should-Start:      udev devfsd
  # Required-Stop:     mountkernfs
  # Should-Stop:       udev devfsd
  # Default-Start:     S
  # Default-Stop:      0 6

So I forced the rc.d links to be created from scratch with:

  update-rc.d -f mdadm-raid remove
  update-rc.d -f mdadm remove
  update-rc.d mdadm-raid start 25 S . start 60 0 6 .
  update-rc.d mdadm defaults 25

Now the links are:

  $ ls -l rc?.d/???mdadm*
  lrwxrwxrwx 1 root root 20 2009-02-11 22:41 rc0.d/K01mdadm-raid -> ../init.d/mdadm-raid*
  lrwxrwxrwx 1 root root 15 2009-02-11 22:41 rc0.d/K02mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 20 2009-02-11 22:41 rc6.d/K01mdadm-raid -> ../init.d/mdadm-raid*
  lrwxrwxrwx 1 root root 15 2009-02-11 22:41 rc6.d/K02mdadm -> ../init.d/mdadm*
  lrwxrwxrwx 1 root root 20 2009-02-11 22:41 rcS.d/S07mdadm-raid -> ../init.d/mdadm-raid*
  lrwxrwxrwx 1 root root 15 2009-02-11 22:41 rcS.d/S10mdadm -> ../init.d/mdadm*

  That is ...
  ... unchanged:
  rc0.d/K01mdadm-raid -> ../init.d/mdadm-raid*
  rc0.d/K02mdadm -> ../init.d/mdadm*
  rc6.d/K01mdadm-raid -> ../init.d/mdadm-raid*
  rc6.d/K02mdadm -> ../init.d/mdadm*
  rcS.d/S07mdadm-raid -> ../init.d/mdadm-raid*
  ... gone:
  rc1.d/K02mdadm -> ../init.d/mdadm*
  rc2.d/S01mdadm -> ../init.d/mdadm*
  rc3.d/S01mdadm -> ../init.d/mdadm*
  rc4.d/S01mdadm -> ../init.d/mdadm*
  rc5.d/S01mdadm -> ../init.d/mdadm*
  ... new:
  rcS.d/S10mdadm -> ../init.d/mdadm*

-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (550, 'testing')
Architecture: amd64 (x86_64)

Versions of packages mdadm depends on:
ii  debconf                       1.5.24     Debian configuration management sy
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  lsb-base                      3.2-20     Linux Standard Base 3.2 init scrip
ii  makedev                       2.3.1-88   creates device files in /dev
ii  udev                          0.125-7    /dev/ and hotplug management daemo

Versions of packages mdadm recommends:
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo
ii  nullmailer [mail-transport-ag 1:1.04-1.1 simple relay-only mail transport a

mdadm suggests no packages.

-- debconf information:
* mdadm/autostart: true
* mdadm/initrdstart: /dev/md0
  mdadm/initrdstart_notinconf: false
  mdadm/initrdstart_msg_errexist:
  mdadm/initrdstart_msg_intro:
  mdadm/initrdstart_msg_errblock:
* mdadm/start_daemon: true
* mdadm/mail_to: root
  mdadm/initrdstart_msg_errmd:
  mdadm/initrdstart_msg_errconf:
* mdadm/autocheck: true