> (To simply support segments consisting of single raid member > devices it may be enough if a superblock marking itself as failed would > mean itis contains conflicting changes. Multi member segments would require > segment IDs) Don't know why I thought that extra IDs would be needed, as UUID+device-number is enough and degrading into multi device segments is and has been working all the time. Aside not catching a conflict in the case of two segments with same event count (both segments only booted with few changes), i.e. the main issue addressed in my original post, plugging different versions also just works. Concerning the scheme to mark segments as containing conflicting changes for Enhancement 2) from my original post: I think saying a superblock marking itself as failed (.) would indicates a known conflicting segment (alternative version), may just as well work for multiple member segments. In the example below, first both dev1+dev2 can be considered to contain known conflicting segments (alternative versions) because they mark themselves as failed. But because they mark each other as up (U) they both constitute one two-member-segment. The dev3 was the first segment on the incidence that both segments came up together, because it does not mark itself as failed. dev1 [.U.] dev2 [U..] dev3 [..U] Kind regards, Christian -- 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
