On 6/24/2012 2:51 PM, Ingo Jürgensmann wrote: > Am 24.06.2012 um 21:28 schrieb Stan Hoeppner: > >> Thus, I'd guess that the metadata format changed from 0.90 to 1.2 with a >> very recent release of mdadm. Are you using distro supplied mdadm, a >> backported more recent mdadm, or did you build mdadm from the most >> recent source? > > As I already wrote, I'm using Debian unstable, therefore distro supplied mdadm. Otherwise I'd have said this. Yes, you did mention SID, and I missed it. SID is the problem here, or I should say, the cause of the error message. SID is leading (better?) edge, and is obviously using a recent mdadm release, which defaults to metadata 1.2, and chunk of 512KB. As more distros adopt newer mdadm, reports of this will be more prevalent. So Eric's idea is likely preferable than mine. XFS making a recommendation against an md default would fly like a lead balloon... > I don't think that Debian unstable is bleeding edge. It's apparently close enough in the case of mdadm, given you're the first to report this, AFAIK. > I find it strange that you've misinterpreted citing the mdadm man page as "sandbagging us". =:-O Sandbagging simply means holding something back, withholding information. Had you actually not mentioned your OS/version, this would have been an accurate take on the situation. But again, youd did, and I simply missed it. So again, my apologies for missing your mention of SID in your opening email. That would have prevented my skeptical demeanor. -- Stan _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
