Skip to content

nocontrold: Eliminating ocfs2_controld

Lars Marowsky-Bree ocfs2-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 6 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 6 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Ocfs2-devel] [PATCH 0/6] nocontrold: Eliminating ocfs2_controld

On 2013-09-05T22:26:56, Goldwyn Rodrigues <[email protected]> wrote:

Hi Goldwyn,

thanks! This looks really good.

Quoted 4 lines

This is an effort of removing ocfs2_controld.pcmk and getting ocfs2 DLM handling up to the times with respect to DLM (>=4.0.1) and corosync (2.3.x). AFAIK, cman also is being phased out for a unified corosync cluster stack.

That's clearly necessary, also to bring OCFS2 more uptodate with the latest happenings in the GFS2 world; it'll allow both file systems to share exactly the same cluster stack.

Quoted 3 lines

https://github.com/goldwynr/ocfs2-tools branch: nocontrold Currently, not many checks are present in the userspace code, but that would change soon.

There's one question I have; how will this handle

- the "old" user-space code starting on a new kernel,
- or the "new" user-space code being run on an old kernel?

Is there anything we can do to at least provide a meaningful error message in the first case? The second should be easier to handle.

Regards,
Lars

Signature · 3 lines
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde