On Fri, 11 Feb 2011 19:57:52 -0500 Christian <cjs703@xxxxxxxxx> wrote: > # mdadm -V > mdadm - v3.1.4 - 31st August 2010 So either I didn't fix it like I thought, or I subsequently broke it. Could you send me the combined --examine output that you saved? That might help me reproduce the exact problem, then add it to the mdadm test suite. Then fix it. Thanks, NeilBrown > > On Fri, Feb 11, 2011 at 7:52 PM, NeilBrown <neilb@xxxxxxx> wrote: > > On Fri, 11 Feb 2011 17:36:08 -0500 Christian <cjs703@xxxxxxxxx> wrote: > > > >> Here it is again, there were a few other messages in there at the beginning. > >> > >> [70745.855861] md: md1 stopped. > >> [70745.859303] md: bind<sdm1> > >> [70745.859576] md: bind<sdr1> > >> [70745.859720] md: bind<sds1> > >> [70745.860265] md: bind<sdq1> > >> [70745.860428] md: bind<sdk1> > >> [70745.860680] md: bind<sdf1> > >> [70745.860839] md: bind<sdg1> > >> [70745.860986] md: bind<sdl1> > >> [70745.861169] md: bind<sde1> > >> [70745.861359] md: bind<sdt1> > >> [70745.861407] md: kicking non-fresh sds1 from array! > >> [70745.861411] md: unbind<sds1> > >> [70745.870570] md: export_rdev(sds1) > >> [70745.870598] md: kicking non-fresh sdm1 from array! > > > > That shouldn't happen when you use -f .... > > > > Could be that you hit the mdadm bug fixed by commit 67a8c82d606 > > which is in mdadm-2.6 > > What version of mdadm are you running??? > > > > (I note you have got your data back by other means - good!) > > > > NeilBrown > > -- 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
