Bug#324841: mdadm: It's me again

[Marcello Maggioni]

Package: mdadm
Version: 1.9.0-4
Followup-For: Bug #324841



Hi again :)

I'm reopening this bug because I found the evidence that the MD device is not
cleanly shutdown at reboot time.

RAID0 devices doesn't have something like "clean" or "not-clean" because they don't
need to be reconstructed after a bad shutdown.

So I've tried with a RAID1 array built up for the occasion with JFS and used
as root device of a debian installation .

The result is that at boot time in the dmesg is possible to find message that 
report that the array is out of sync and needs recontruction.

I've attached my dmesg.

Bye

Marcello

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=it_IT at euro, LC_CTYPE=it_IT at euro (charmap=ISO-8859-15)

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: true
  mdadm/warning:
  mdadm/mail_to: root
  mdadm/start_daemon: true
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg
Type: application/octet-stream
Size: 15415 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20050910/f37d30b7/dmesg.obj