Your message dated Sun, 12 Dec 2010 22:59:58 +0100
with message-id <1292191198.11595.9.ca...@localhost>
and subject line Re: mdadm: metadata format 00.90 unknown, ignored
has caused the Debian Bug report #606389,
regarding mdadm: metadata format 00.90 unknown, ignored
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
606389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606389
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mdadm
Version: 2.6.7.2-3
Severity: important
I used mdadm --detail --scan >> /etc/mdadm/mdadm.conf before rebooting to
make
sure everything came back as configured. After rebooting I had two md
devices
again, but both were auto-read-only and one was pointing to an old device
that
shouldn't have been active. Every action I took with mdadm was prefixed
with:
mdadm: metadata format 00.90 unknown, ignored.
mdadm: metadata format 00.90 unknown, ignored.
After some heart pounding, hair pulling and searching (ignoring any advice
to zero the superblock) I came across a post that suggested the parsing of
metadata=00.90 was at fault. Sure enough, I changed it to metadata=0.90
and everything's good again.
http://ubuntuforums.org/showthread.php?p=6345457#post6345457
After getting this sorted out I checked around further and found that mdadm
-Ds
was the generally recommended way to add those settings, if one uses a
mdadm.conf file (bug 569359) and they format the metadata parameter with
00.90 just
like all other mdadm output, but for some reason assemble hates them. I also
noted
that the /usr/share/mdadm/mkconf tool doesn't include the metadata
parameter.
I see there is suppose to be a patch that is hopefully in the version of
mdadm
for Squeeze already.
http://neil.brown.name/git?p=mdadm;a=commit;h=d7ee65c960fa8a6886df7416307f57545ddc4460
-- Package-specific info:
-- System Information:
Debian Release: 5.0.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mdadm depends on:
ii debconf 1.5.24 Debian configuration management
sy
ii libc6 2.7-18lenny6 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+lenny3 /dev/ and hotplug management
daemo
Versions of packages mdadm recommends:
ii module-init-tools 3.4-1 tools for managing Linux kernel
mo
ii postfix [mail-transport-agent 2.5.5-1.1 High-performance mail transport
ag
mdadm suggests no packages.
-- debconf information:
* mdadm/autostart: true
mdadm/mail_to: root
mdadm/initrdstart_msg_errmd:
* mdadm/initrdstart: all
mdadm/initrdstart_msg_errconf:
mdadm/initrdstart_notinconf: false
mdadm/initrdstart_msg_errexist:
mdadm/initrdstart_msg_intro:
mdadm/autocheck: true
mdadm/initrdstart_msg_errblock:
mdadm/start_daemon: true
--
Jacob
--- End Message ---
--- Begin Message ---
Version: 3.1.4-1+8efb9d1
Am Mittwoch, den 08.12.2010, 13:46 -0700 schrieb Jacob Anawalt:
> I see there is suppose to be a patch that is hopefully in the version of
> mdadm for Squeeze already.
>
> http://neil.brown.name/git?p=mdadm;a=commit;h=d7ee65c960fa8a6886df7416307f57545ddc4460
That's really an annoying bug. Thankfully it's been fixed upstream and
the patch is included in squeeze. I'm therefore closing the bug with the
appropriate version. Feel free to reopen if necessary.
Best regards
Alexander Kurtz
signature.asc
Description: This is a digitally signed message part
--- End Message ---
