Bug#386432: bad specifier in /etc/cron.d/mdadm

R. Scott Bailey scott.bailey at eds.com
Thu Sep 7 15:19:18 UTC 2006


Package: mdadm
Version: 2.5.2-7
Severity: minor


The "automatic check on first Sunday of month" logic is b0rken. :-) The 
specifier used in /etc/cron.d/mdadm is "6 1 1-7 * 7", but the problem is 
that "man 5 crontab" (and unhappy experience) shows that the rule 
triggers when minute, hour, month (6, 1, * respectively) match and 
*EITHER* day-of-month *OR* day-of-week (1-7, 7 respectively) match.

Consequently, the result is that the consistency check hammers my system 
every night for the first week of the month (days 1-7 of month) AND 
every Sunday (day 7 of week). This is a little more rigorous than I was 
anticipating. :-)

I fixed my script to just run on the 1st of each month because I was too 
lazy to work out a hack that would keep the scheduling "as advertised", 
which would have been preferable.

Thanks,
Scott

-- Package-specific info:
--- mount output
/dev/md1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,size=1g)
/dev/md0 on /boot type ext3 (rw)
/dev/mapper/vg00-varvol on /var type ext3 (rw)
/dev/mapper/vg00-usrvol on /usr type ext3 (rw)
/dev/mapper/vg01-homevol on /home type ext3 (rw,usrquota)
/dev/mapper/vg01-bdbvol on /var/lib/bacula type ext3 (rw)
/dev/mapper/vg01-spoolvol on /var/spool/backup type ext3 (rw)
/dev/mapper/vg01-h10vol on /export/hummingbird type ext3 (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
nfsd on /proc/fs/nfsd type nfsd (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
/dev/mapper/vg00-srcvol on /usr/local/src type ext3 (rw)
/dev/mapper/vg01-decvol on /export/decpatch type ext3 (rw)

--- mdadm.conf
DEVICE partitions
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=d41a6395:1ed0706b:987c8a3f:892656ca
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=979f723e:d4aaf69c:2c3b5ffe:5b959c20
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=5adb1c51:71d3a0c9:8ab37bd9:5f288943
ARRAY /dev/md3 level=raid1 num-devices=2 UUID=577bf8aa:1e44159b:3c06aaef:dfff845c
ARRAY /dev/md4 level=raid1 num-devices=2 UUID=0c1db599:ad8e7851:ded5d6f5:7aaf62c1
ARRAY /dev/md5 level=raid1 num-devices=2 UUID=1f4caa74:52b94ea4:54dabc5b:aa729669
ARRAY /dev/md6 level=raid1 num-devices=2 UUID=de0e7f42:765f88ef:5a9d33f1:8c4d2682
ARRAY /dev/md7 level=raid1 num-devices=2 UUID=5f827d0d:60e79912:d81abcfc:e338809f
MAILADDR root

--- /proc/mdstat:
Personalities : [raid1] 
md7 : active raid1 sdf1[0] sdl1[1]
      8856896 blocks [2/2] [UU]
      
md6 : active raid1 sde1[0] sdk1[1]
      8856896 blocks [2/2] [UU]
      
md5 : active raid1 sdd1[0] sdj1[1]
      8856896 blocks [2/2] [UU]
      
md4 : active raid1 sdc1[0] sdi1[1]
      8856896 blocks [2/2] [UU]
      
md3 : active raid1 sdb1[0] sdh1[1]
      8856896 blocks [2/2] [UU]
      
md2 : active raid1 sda4[0] sdg4[1]
      8494016 blocks [2/2] [UU]
      
md1 : active raid1 sdg2[1] sda2[0]
      309056 blocks [2/2] [UU]
      
md0 : active raid1 sda1[0] sdg1[1]
      53696 blocks [2/2] [UU]
      
unused devices: <none>

--- /proc/partitions:
major minor  #blocks  name

   8     0    8886762 sda
   8     1      53760 sda1
   8     2     309120 sda2
   8     4    8494080 sda4
   8    16    8886762 sdb
   8    17    8856960 sdb1
   8    32    8886762 sdc
   8    33    8856960 sdc1
   8    48    8886762 sdd
   8    49    8856960 sdd1
   8    64    8886762 sde
   8    65    8856960 sde1
   8    80    8886762 sdf
   8    81    8856960 sdf1
   8    96    8886762 sdg
   8    97      53760 sdg1
   8    98     309120 sdg2
   8   100    8494080 sdg4
   8   112    8886762 sdh
   8   113    8856960 sdh1
   8   128    8886762 sdi
   8   129    8856960 sdi1
   8   144    8886762 sdj
   8   145    8856960 sdj1
   8   160    8886762 sdk
   8   161    8856960 sdk1
   8   176    8886762 sdl
   8   177    8856960 sdl1
   9     0      53696 md0
   9     1     309056 md1
   9     2    8494016 md2
   9     3    8856896 md3
   9     4    8856896 md4
   9     5    8856896 md5
   9     6    8856896 md6
   9     7    8856896 md7
 253     0   11550720 dm-0
 253     1   10485760 dm-1
 253     2    8273920 dm-2
 253     3    3153920 dm-3
 253     4     327680 dm-4
 253     5    2097152 dm-5
 253     6    1310720 dm-6
 253     7     524288 dm-7
 253     8    1572864 dm-8

--- initrd.img-2.6.17-4+scsi:

--- /proc/modules:

-- System Information:
Debian Release: testing/unstable
Architecture: alpha
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-4+scsi
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]        1.5.3       Debian configuration management sy
ii  libc6.1                      2.3.6.ds1-4 GNU C Library: Shared libraries
ii  lsb-base                     3.1-14      Linux Standard Base 3.1 init scrip
ii  makedev                      2.3.1-82    creates device files in /dev

Versions of packages mdadm recommends:
ii  sendmail-bin [mail-transport- 8.13.7-2   powerful, efficient, and scalable 

-- debconf information:
* mdadm/autostart: true
  mdadm/initrdstart: /dev/md1
* mdadm/warning:
* mdadm/start_daemon: true
* mdadm/mail_to: root
* mdadm/autocheck: true




More information about the pkg-mdadm-devel mailing list