Also if i do something like:
# grow bad blocks as ma*tor does :)
mdadm --grow -l faulty -p rp454 /dev/md2
mdadm --grow -l faulty -p rp738 /dev/md3
# add a spare
mdadm -a /dev/md5 /dev/ram5
mdadm -f /dev/md5 /dev/md2 && mdadm -f /dev/md5 /dev/md2
After the initial reconstruction i get this:
mdadm: set /dev/md2 faulty in /dev/md5
Segmentation fault
And then the computer enters in some kind of loop that makes it almost
completely unresponsive
--
All generalizations are false, including this one.
-- Mark Twain
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
