All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gang He <GHe@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] mount existent ocfs2 volume in the local mode without the extra DLM, pacemaker/corosync layers
Date: Fri, 10 Apr 2020 10:16:33 +0000	[thread overview]
Message-ID: <CH2PR18MB3206F9F31924F1AF395EB1B3CFDE0@CH2PR18MB3206.namprd18.prod.outlook.com> (raw)
In-Reply-To: <140dda1e-35bd-67fe-a3d4-df3222550984@gmail.com>

Hello Jeseph,

________________________________________
From: Joseph Qi <jiangqi903@gmail.com>
Sent: Friday, April 10, 2020 6:00 PM
To: Gang He; ocfs2-devel at oss.oracle.com; ocfs2-users at oss.oracle.com
Subject: Re: [Ocfs2-devel] mount existent ocfs2 volume in the local mode without the extra DLM, pacemaker/corosync layers

Just be curious about this user scenario.
What is "without DLM/cluster environment"?

The user can mount the existent ocfs2 cluster volume directly, does not depend on if DLM/cluster services are available.
When this option is added, the mount process  will not do dlm related things, like local mount.
This way will help the user access the files in the volume quickly for avoiding setup/online the cluster environment.

Thanks
Gang
 
Thanks,
Joseph

On 2020/4/10 16:36, Gang He wrote:
> Hello Guys,
>
> Usually, we create a ocfs2 cluster on the top DLM(pacemaker/corosync) with a shared volume.
> but the customers complained they could not mount existent ocfs2 volume in the local mode without DLM/cluster envirnment in backup/restore scenario.
> in this case, the customers want to mount this ocfs2 volume from one node without cluster aware way, sometimes the customers have stoped(uninstalled) the whole cluster before the backup/restore, they just want to access the data from the ocfs2 volume.
> Then, I'd like to add a mount option, e.g. "nocluster" (I feel using "local" option is a little confused for the users, since we have a local mount volume concept).
> If the users use "nocluster" option to mount a ocfs2 volume, the whole mount will not depend on the DLM/cluster related services. they
> will mount the existent ocfs2 volume directly (like local mount) for avoiding setup the cluster stacks.
> The code change is small with my preliminary investigation, the main affected places are mount.ocfs2/mounted.ocfs2 tools and mount process in the ocfs2 kernel modules.
>
> Any comments/suggestions?
>
>
> Thanks a lot
> Gang
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>

  reply	other threads:[~2020-04-10 10:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10  8:36 [Ocfs2-devel] mount existent ocfs2 volume in the local mode without the extra DLM, pacemaker/corosync layers Gang He
2020-04-10  9:08 ` Changwei Ge
2020-04-10  9:28   ` Gang He
2020-04-10  9:39     ` Changwei Ge
2020-04-10 10:00 ` Joseph Qi
2020-04-10 10:16   ` Gang He [this message]
2020-04-10 12:49     ` Joseph Qi
2020-04-10 13:57       ` Gang He
2020-04-10 17:10 ` herbert.van.den.bergh at oracle.com
2020-04-13 10:42   ` [Ocfs2-devel] [Ocfs2-users] " Gang He

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=CH2PR18MB3206F9F31924F1AF395EB1B3CFDE0@CH2PR18MB3206.namprd18.prod.outlook.com \
    --to=ghe@suse.com \
    --cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.