On Tue, Mar 30, 2010 at 10:47 AM, Labun, Marcin <Marcin.Labun@xxxxxxxxx> wrote: > I understand that there are following defaults: > - Platform/metadata limitations create default domains > - metadata handler deliver default actions > The equivalent configuration line for imsm is: > DOMAIN path="any" metadata=imsm action=none I would expect path=<ahci ports> when metadata=imsm > User could additionally split default domains using spare groups and path keyword. > For instance for imsm, the default domain area is platform controller. > If any metadata is server by multiple controllers, each of them creates its own domain. A single DOMAIN can span several controllers, but only if that does not violate the 'platform' constraints for that metadata type (which are always enforced). > Enable spare disk sharing between containers if they belong to the same domain and have not conflicting spare group assignment. This will allow for spare sharing by default. Yes, spare sharing by default within the domain and as Doug said ignore any conflicts with the spare-group identifier i.e. DOMAIN overrides/supersedes spare-group. > Additionally, we can consult metadata handlers before moving spares between containers. We can do that by adding another metadata handler function which shall test metadata and controller dependencies (I can imagine that user can define metadata stored domains of spare sharing; controllers (OROM) dependent constrains shall be handled in this function, too). This really is just a variation of load_super() performed on a container with an extra disk added to report whether the device is spare, failed, or otherwise out of sync. In the imsm case this is load_super_imsm_all() with another disk (outside of the current container list) to compare against. -- Dan -- 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
