Your message dated Sun, 30 Jul 2006 04:17:42 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379352: fixed in mdadm 2.5.2-8
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: mdadm
Version: 2.5.2-7
Severity: minor


checkarray ran this morning, and presented me with the following output:

checkarray: E: /sys/block/md3/md/sync_action not writeable.

The idea didn't surprise me, since a linear array isn't "synced" I
wouldn't expect the sysfs entry for that. However, while the warning is
harmless, I think it's also unnecessary. One warning a month won't
bother me (much...), but there are people (somewhere, maybe) that it
could confuse. checkarray should probably just silently skip linear
arrays, since there's nothing to check.

Jacob

-- Package-specific info:
--- mount output
/dev/md2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hdg3 on /home type xfs (rw)
/dev/md0 on /mnt/video type xfs (rw)
/dev/md1 on /mnt/mp3 type xfs (rw)
/dev/md3 on /mnt/scratch type xfs (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
automount(pid3163) on /misc type autofs 
(rw,fd=4,pgrp=3163,minproto=2,maxproto=4)
nfsd on /proc/fs/nfsd type nfsd (rw)

--- mdadm.conf
DEVICE partitions
ARRAY /dev/md0 level=raid5 num-devices=4 
UUID=3dce578a:8b7bdb5e:adc9138e:aa71d832
ARRAY /dev/md1 level=raid5 num-devices=3 
UUID=5d7f878a:9076ab14:38cc1828:059ae4ec
ARRAY /dev/md2 level=raid1 num-devices=2 
UUID=69f77581:2a6a86fc:2b91a149:d9b6c148
ARRAY /dev/md3 level=linear num-devices=2 
UUID=2b1b3433:b5a59997:fb093e06:ea9a751e
MAILADDR root

--- /proc/mdstat:
Personalities : [raid1] [raid5] [raid4] [linear] 
md3 : active linear hdg6[0] hdh1[1]
      25245888 blocks 64k rounding
      
md1 : active raid5 hde6[0] hdg2[2] hdf5[1]
      115266176 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
        resync=DELAYED
      
md0 : active raid5 hdh5[0] hdg1[3] hdf7[2] hde5[1]
      178706304 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
      [=======>.............]  resync = 37.5% (22369408/59568768) 
finish=34.2min speed=18105K/sec
      
md2 : active raid1 hdf9[0] hdg5[1]
      5108544 blocks [2/2] [UU]
        resync=DELAYED
      
unused devices: <none>

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

  33     0  117220824 hde
  33     1          1 hde1
  33     5   59585022 hde5
  33     6   57633156 hde6
  33    64  195360984 hdf
  33    65          1 hdf1
  33    69   57641157 hdf5
  33    70   31455207 hdf6
  33    71   59577020 hdf7
  33    72   29856802 hdf8
  33    73    5116671 hdf9
  33    74   11711353 hdf10
  34     0  156290904 hdg
  34     1   59568988 hdg1
  34     2   57641220 hdg2
  34     3   20482875 hdg3
  34     4          1 hdg4
  34     5    5124703 hdg5
  34     6   13470471 hdg6
  34    64   78150744 hdh
  34    65   11775613 hdh1
  34    68          1 hdh4
  34    69   60251751 hdh5
  34    70    5606653 hdh6
  34    71     514048 hdh7
   9     2    5108544 md2
   9     0  178706304 md0
   9     1  115266176 md1
   9     3   25245888 md3

--- initrd.img-2.6.16-2-686:

--- /proc/modules:
linear 5312 1 - Live 0xe1324000
raid5 21888 2 - Live 0xe0af1000
xor 13896 1 raid5, Live 0xe131f000
dm_mod 47892 0 - Live 0xe1b91000
raid1 19264 1 - Live 0xe0863000
md_mod 63956 7 linear,raid5,raid1, Live 0xe08b6000

--- volume detail:


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

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

Versions of packages mdadm recommends:
ii  exim4-daemon-light [mail-tran 4.62-2     lightweight exim MTA (v4) daemon

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


--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 2.5.2-8

We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive:

mdadm-udeb_2.5.2-8_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_2.5.2-8_i386.udeb
mdadm_2.5.2-8.diff.gz
  to pool/main/m/mdadm/mdadm_2.5.2-8.diff.gz
mdadm_2.5.2-8.dsc
  to pool/main/m/mdadm/mdadm_2.5.2-8.dsc
mdadm_2.5.2-8_i386.deb
  to pool/main/m/mdadm/mdadm_2.5.2-8_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
martin f. krafft <[EMAIL PROTECTED]> (supplier of updated mdadm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 27 Jul 2006 22:49:32 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.5.2-8
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <[EMAIL PROTECTED]>
Changed-By: martin f. krafft <[EMAIL PROTECTED]>
Description: 
 mdadm      - tool to administer Linux MD device arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD device arrays (software RAID) (udeb)
Closes: 378678 379019 379352 379511 380152 380424 380425
Changes: 
 mdadm (2.5.2-8) unstable; urgency=low
 .
   * Re-added rootraiddoc.97.html which was mysteriously lost (closes: #378678).
   * Catching modprobe error in case of absence of the kernel modules, or
     a non-modular kernel. Thanks to Holger Levsen.
   * Copy raid456 kernel module into initramfs, if present (closes: #380152).
   * checkarray: check for presence of active RAID arrays and give an
     appropriate error if there are none present (closes: #379019).
   * checkarray: skip sync for RAID0 devices (closes: #379352, #380424).
   * Fixing cron registration for checkarray. crontab(5) is really stupid and
     makes me think that they simply documented a bug instead of fixing it, so
     now I have to hack around it. See the cron.d file (closes: #380425).
   * Removed the code writing auto-detected devices to /var, which was silly
     since /var isn't necessarily mounted yet by the time mdadm-raid is called.
     Thanks to Maurizio Avogadro for pointing this out.
   * Add reference to BAARF to README.Debian and included the RAID5 vs RAID10
     article from the BAARF website.
   * Updated debconf translations:
     - Japanese by Hideki Yamane, thanks!
     - French by Florentin Duneau, thanks! (closes: #379511)
Files: 
 a3805c7329cc5d08914d4becc0dfebb6 712 admin optional mdadm_2.5.2-8.dsc
 ebd87cd1ba3c3acecc2a758c1e67b234 71493 admin optional mdadm_2.5.2-8.diff.gz
 0376276b546b68b24afdbc8a3696ac4a 184598 admin optional mdadm_2.5.2-8_i386.deb
 f5ab0ab41cf08332de65844fc2893489 67694 debian-installer optional 
mdadm-udeb_2.5.2-8_i386.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEzJHgIgvIgzMMSnURAi2uAJ9nAhuQoCBe2vigEIqN6PIm5eze6QCeJEHk
X28NGfNLF5X0oNjOzoUmhoc=
=s5KC
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to