Package: mdadm
Version: 1.9.0-4
Severity: normal

I'm getting reports like this:

        From: mdadm monitoring <[EMAIL PROTECTED]>
        To: [EMAIL PROTECTED]
        Subject: DegradedArray event on /dev/md1:chako
        Date: Thu, 09 Jun 2005 20:35:25 -0400

        This is an automatically generated mail message from mdadm
        running on chako

        A DegradedArray event had been detected on md device /dev/md1.

        Faithfully yours, etc.

when /proc/mdstat looks like this:

        chako:~# cat /proc/mdstat 
        Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] 
[raid10] 
        md1 : active raid1 hda1[1] hdc1[0]
              2048192 blocks [3/2] [UU_]
              
        md3 : active raid1 hda3[1] hdc3[0]
              131392 blocks [3/2] [UU_]
                      
        md0 : active raid1 hda2[0] hdc2[1]
              117880960 blocks [3/2] [UU_]

        unused devices: <none>

The missing disks in these RAID1 arrays are by design, to allow extra
mirrors to be hot added to the array without reconfiguring.  The usual
purpose for this is to clone the first two disks onto e.g. a USB external
drive--I attach the USB drive, do raidhotadd (now mdadm -a), let the
drive sync, then setfaulty/hotremove (mdadm -f/-r) the USB drive and
repeat if necessary.

It would be nice to not have the emails in this particular case.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (102, 'testing'), (101, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-zb5s
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mdadm depends on:
ii  debconf                     1.4.30.13    Debian configuration management sy
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  makedev                     2.3.1-77     creates device files in /dev

-- debconf information:
* mdadm/autostart: false
* mdadm/mail_to: root
* mdadm/warning:
* mdadm/start_daemon: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to