I've just been doing a bit of work on the wiki when I put 2 and 2 together, and hope I haven't made 5 ... Bitmaps interfere with grow operations, I believe ... And mdadm has recently been modified so that bitmaps are switched on by default, I also believe ... Could this be silently blocking the grow, so you don't get any error and it just sits there doing nothing? But that brings up two points. Should mdadm now explicitly look for a bitmap when growing an array, and warn that the bitmap needs to be disabled? Apparently it currently comes up with some errors that hint at the cause rather than explicitly say so. And secondly, I'm sure someone sent an email to the list that explained when a bitmap was created. I can't find it in my archives. The man page says it's created if the array is over 100G, but I'm sure the email gave rather more detail than that and that the figure actually varied. But I'm sure you can see from this that I'm updating this bit of the wiki. Is there anything else I ought to know about bitmaps, so I can document it? :-) Cheers, Wol -- 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
