As a note, I believe the mdraid resource agent is intended to replace Raid1. But its documentation is the same in the two areas you mentioned.
I definitely agree that the purpose of OCF_CHECK_LEVEL for this agent should be documented in <longdesc>. (OCF_CHECK_LEVEL is documented in a generic sense in the Pacemaker Explained doc.) While it could be argued that configuring clustered MD constitutes "knowing what you're doing" with regard to the force_clones attribute, it wouldn't hurt to mention clustered MD as a use case where this attribute is required. On Fri, Nov 27, 2020 at 2:25 AM Ulrich Windl <[email protected]> wrote: > > Hi! > > Reading the metadata of the Raid1 RA in SLES15 SP2, I see: > force_clones (boolean, [false]): force ability to run as a clone > Activating the same md RAID array on multiple nodes at the same time > will result in data corruption and thus is forbidden by default. > > A safe example could be an array that is only named identically across > all nodes, but is in fact distinct. > > Only set this to "true" if you know what you are doing! > -- > > As SLES15 features "Clustered MD", you need to set that attibute to use > Clustered MD, of course. > Thus I think the documentation should be updated. > > The other thing is the lack of documentation for $OCF_CHECK_LEVEL > > Regards, > Ulrich > > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ > -- Regards, Reid Wahl, RHCA Senior Software Maintenance Engineer, Red Hat CEE - Platform Support Delivery - ClusterHA _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
