On Sat, Apr 18, 2009 at 8:35 AM, Doug Ledford <dledford@xxxxxxxxxx> wrote: > I've been thinking about this, and this is the method I would suggest. > > Add two new keywords to the mdadm.conf file: > > ASSEMBLE > INCREMENTAL > > Allow each of those keywords to have one of three set values: > None - Don't attempt to assemble any arrays regardless of whether or not they are in the mdadm.conf file or not > Known - Only assemble arrays with a matching array line > All - Attempt to assemble any array found > > The combination of the two options and the three settings would allow you to control mdadm behavior for both array assembly modes independently. That, combined with my previous patch, should allow arrays to assemble well, with known names, allow you to control auto assembly by udev, and in the event that your machine just exports volumes to other machines for their use, stop assembly entirely. > > -- Of the proposals thus far, I think I like this one the best. More or less, it's what I thought homehost was supposed to do (if homehost did not match, ignore!) but given the morass around homehost, this seems like a very reasonable approach to solving this class of issues. With the increasing prevalence of block devices which may appear on many hosts (like AoE, etc...) it seems as though this issue isn't going to go away easily. -- Jon -- 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
