From: "heming.zhao--- via Ocfs2-devel" <ocfs2-devel@oss.oracle.com>
To: Mark Fasheh <mark@fasheh.com>
Cc: ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH 3/4] re-enable "ocfs2: mount shared volume without ha stack"
Date: Mon, 1 Aug 2022 09:01:49 +0800 [thread overview]
Message-ID: <0b33b0c2-71dc-3961-88ee-fb29dedcc7c1@suse.com> (raw)
In-Reply-To: <CAGe7X7kLfsUfb1+yYgD4PffnJYvJVeqrLtub8qC=ujC2gxEzTA@mail.gmail.com>
Hello Mark,
On 8/1/22 01:42, Mark Fasheh wrote:
> Hi Heming,
>
> On Fri, Jul 29, 2022 at 6:15 PM Heming Zhao via Ocfs2-devel
> <ocfs2-devel@oss.oracle.com> wrote:
>>
>> the key different between local mount and non-clustered mount:
>> local mount feature (tunefs.ocfs2 --fs-features=[no]local) can't do
>> convert job without ha stack. non-clustered mount feature can run
>> totally without ha stack.
>
> Can you please elaborate on this? Local mounts can run without a
> cluster stack so I don't see the difference there. We have
I am using pacemaker cluster stack. In my env, the trouble of the converting between
local and clustered mounts are only happening on cluster stack.
the non-clustered mount feature (Gang He commit: 912f655d78c5) gave ocfs2 the ability
to mount volume at any env (with/without cluster stack).
The 912f655d78c5 derived from SUSE customer complain: User wanted to fsck the backup
ocfs2 volume in non-clustered env. They wanted to access the volume quickly and didn't
want to take time/resource to set up HA stack. (by the way, pcmk stack at least needs
two nodes to set up a cluster.)
> tunefs.ocfs2 look for and join the cluster so as to avoid corrupting
> users data - that's a feature, not a bug. So what I'm seeing here is
> just opening us to potential corruptions. Is there a specific use case
> here that you're trying to account for? Are you fixing a particular
> bug?
>
Tunefs.ocfs2 still needs HA/dlm stack to protect joining action. commit 912f655d78c5
works on non-clustered env, which needs other tech (eg. MMP) to protect corrupting.
From my viewpoint, the non-clustered mount code is based on local mount code,
which gives more flexible than local mount. non-clustered mount uses unify mount
style align with clustered mount. I think users will like more to use non-clustered
mount than using tunefs.ocfs2 to change mount type.
Thanks,
Heming
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2022-08-01 1:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 1:14 [Ocfs2-devel] [PATCH 0/4] re-enable non-clustered mount & add MMP support Heming Zhao via Ocfs2-devel
2022-07-30 1:14 ` [Ocfs2-devel] [PATCH 1/4] ocfs2: Fix freeing uninitialized resource on ocfs2_dlm_shutdown Heming Zhao via Ocfs2-devel
2022-08-08 6:51 ` Joseph Qi via Ocfs2-devel
2022-08-08 12:09 ` Heming Zhao via Ocfs2-devel
2022-08-10 1:31 ` Joseph Qi via Ocfs2-devel
2022-08-10 23:52 ` heming.zhao--- via Ocfs2-devel
2022-07-30 1:14 ` [Ocfs2-devel] [PATCH 2/4] ocfs2: add mlog ML_WARNING support Heming Zhao via Ocfs2-devel
2022-07-30 1:14 ` [Ocfs2-devel] [PATCH 3/4] re-enable "ocfs2: mount shared volume without ha stack" Heming Zhao via Ocfs2-devel
2022-07-31 17:42 ` Mark Fasheh via Ocfs2-devel
2022-08-01 1:01 ` heming.zhao--- via Ocfs2-devel [this message]
2022-08-01 2:25 ` heming.zhao--- via Ocfs2-devel
2022-08-04 23:53 ` Mark Fasheh via Ocfs2-devel
2022-08-05 4:11 ` Mark Fasheh via Ocfs2-devel
2022-08-06 15:53 ` heming.zhao--- via Ocfs2-devel
2022-08-06 16:20 ` Heming Zhao via Ocfs2-devel
2022-08-06 15:44 ` heming.zhao--- via Ocfs2-devel
2022-08-06 16:15 ` Heming Zhao via Ocfs2-devel
2022-07-30 1:14 ` [Ocfs2-devel] [PATCH 4/4] ocfs2: introduce ext4 MMP feature Heming Zhao via Ocfs2-devel
2022-07-31 9:13 ` heming.zhao--- via Ocfs2-devel
2022-08-08 8:19 ` Joseph Qi via Ocfs2-devel
2022-08-08 9:07 ` Heming Zhao via Ocfs2-devel
2022-08-08 9:26 ` Heming Zhao via Ocfs2-devel
2022-08-08 9:29 ` Joseph Qi via Ocfs2-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b33b0c2-71dc-3961-88ee-fb29dedcc7c1@suse.com \
--to=ocfs2-devel@oss.oracle.com \
--cc=heming.zhao@suse.com \
--cc=mark@fasheh.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).