Hi Neil! On Fri, Dec 16, 2011 at 07:53:37AM +1100, NeilBrown wrote: > > Golly, you must be running an ancient kernel ... I fixed this bug at least 2 > days ago... Though admittedly I haven't submitted the fix yet so maybe you > have a good excuse :-) I initially misread "2 days" as "2 years", and was slightly puzzled. I do recall seeing the messages on the list, but obviously didn't pay enough attention to them. ;-) > If you remove both spares: > mdadm /dev/md0 --remove /dev/sdo1 /dev/sdd1 > > the rebuild should start. You can then add them back again "--add". Yep! I feel slightly less stupid about posting now--I would not have thought of that. (Though ISTR that one of the pages I found did touch on this bug (in a slightly different context), but I don't remember whether it mentioned this particular option as a workaround; I sort of think not.) I think this workaround is perfectly acceptable, where I would not want to go out and build the latest kernel just to fix it. But if there were a more critical fix to the kernel, what's the most consistent way to go about that? Would it make more sense to grab the source code from ELrepo and apply patches? Or would it be better to grab the latest kernel tree, adapt the ELrepo .config, and hope for the best? (On this box, there is very little else running, so it should be robust to kernel changes that break other items, as long as it keeps md working.) > Send an email to linux-raid asking who broke what.. Oh wait, you did that. :) --keith -- kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx
Attachment:
pgpZQXjb5QpoZ.pgp
Description: PGP signature
