Just tried to reproduce bug on Debian Wheezy, and couldn't. Wheezy
assembles the nested raid without issues. Talked to xnox on #ubuntu-
bugs, and he told me to look into mdadm's udev rules. I did, and
compared it with the one in Wheezy, and the difference is pasted below.
If I change the first line (both in /lib/udev/rules.d and in the initrd)
from Wheezy, it works as before (ok with normal raids, not nested raids)
- if I replace the whole file with the one from Wheezy or just add the
GOTO below, it fails to assemble all raids.
Anyone that can help out here? I'm lost after a lot of digging…
thanks
roy
--- /lib/udev/rules.d/64-md-raid.rules 2013-05-30 14:28:58.966754000 +0200
+++ 64-md-raid.rules-debian 2013-05-30 14:13:41.850203999 +0200
@@ -3,11 +3,15 @@
SUBSYSTEM!="block", GOTO="md_end"
# handle potential components of arrays (the ones supported by md)
-ENV{ID_FS_TYPE}=="linux_raid_member", GOTO="md_inc"
+ENV{ID_FS_TYPE}=="ddf_raid_member|isw_raid_member|linux_raid_member",
GOTO="md_inc"
GOTO="md_inc_skip"
LABEL="md_inc"
+## DISABLED: Incremental udev assembly disabled
+## ** this is a Debian-specific change **
+GOTO="md_inc_skip"
+
# remember you can limit what gets auto/incrementally assembled by
# mdadm.conf(5)'s 'AUTO' and selectively whitelist using 'ARRAY'
ACTION=="add", RUN+="/sbin/mdadm --incremental $tempnode"
root@raidtest:~#
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1171945/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
