Bug#574817: libata transition breaks mdadm arrays
On Sun, Mar 21, 2010 at 3:03 PM, Bastian Blank <waldi@debian.org> wrote:
> On Sun, Mar 21, 2010 at 01:38:53PM +0100, Mathieu Parent (Debian) wrote:
>> On Sun, Mar 21, 2010 at 1:35 PM, Bastian Blank <waldi@debian.org> wrote:
>> > This is expected and not an error. Don't list device-names in
>> > /etc/mdadm.conf.
>> I am not using device names, see attached file.
>
> Hmm, the file is /etc/mdadm/mdadm.conf and mdadm may have generated a
> config during a long ago upgrade, see
> /usr/share/doc/mdadm/README.upgrading-2.5.3.gz.
The attached file was actually /etc/mdadm/mdadm.conf (I don't have
/etc/mdadm.conf). And I have already read the
README.upgrading-2.5.3.gz and done what is expected. i have already
done "rm -f /var/lib/mdadm/CONF-UNCHECKED".
I have the problem with 2.6.32-10, not with 2.6.32-9. I really don't
were mdadm find device-names, I only use uuid in conffiles.
Here is the diff with generated:
$ diff -u mdadm.conf-generated /etc/mdadm/mdadm.conf
--- mdadm.conf-generated 2010-03-21 15:10:35.000000000 +0100
+++ /etc/mdadm/mdadm.conf 2010-03-20 14:13:27.000000000 +0100
@@ -17,7 +17,7 @@
MAILADDR root
# definitions of existing MD arrays
-ARRAY /dev/md0 UUID=4dcfadf1:41f92fa5:1aa89c2e:8c42fb48
+ARRAY /dev/md0 level=raid5 num-devices=4
UUID=4dcfadf1:41f92fa5:1aa89c2e:8c42fb48
-# This configuration was auto-generated on Sun, 21 Mar 2010 15:10:35 +0100
-# by mkconf 3.0.3-2
+# This file was auto-generated on Wed, 13 Aug 2008 22:14:27 +0200
+# by mkconf $Id$
Reply to: