[linux-lvm] [PATCH 00/10] Enhancements to a clustered logical volume activation

Vladislav Bogdanov bubble at hoster-ok.com
Tue Mar 19 17:42:10 UTC 2013

19.03.2013 19:42, Alasdair G Kergon wrote:
> So what I need is:
> Separate out the fixes and minor changes that have no effect on support or
> introduce new constraints on future changes.  Get those out of the way.
> Then with what's left, sort out the impact in terms of additional support,
> testing, constraints etc.  Then work out what the options are.
> E.g. we support multiple lock managers.  How do your changes affect
> each of these, including sanlock?
> New features should only be available where they are tested and supported:
> if some combination doesn't make sense or won't be tested properly, don't allow
> that combination.  In extreme cases, use configure settings as the method of
> control (e.g. if a distro decided it didn't want --node that would need to be a
> configure option).  Man pages need to be correct - if an option doesn't work
> with some lock manager, it should say that (or not mention it if under
> configure's control).


Do you have any opinion of features themselves or a way they implemented
(as if subject had [RFC} in it)?

More information about the linux-lvm mailing list