ocfs2-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Joseph Qi via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Junxiao Bi <junxiao.bi@oracle.com>,
	"heming.zhao@suse.com" <heming.zhao@suse.com>
Cc: "ocfs2-devel@oss.oracle.com" <ocfs2-devel@oss.oracle.com>
Subject: Re: [Ocfs2-devel] [PATCH] Revert "ocfs2: mount shared volume without ha stack"
Date: Tue, 7 Jun 2022 14:31:01 +0800	[thread overview]
Message-ID: <6f72c61f-fae4-9fa3-bcd9-5aa3f03db6ac@linux.alibaba.com> (raw)
In-Reply-To: <41AD73F0-1692-4CCB-95FC-AC65272081D0@oracle.com>



On 6/7/22 11:06 AM, Junxiao Bi wrote:
>>>> Seems I am missing some mails for this thread.
>>>> The 'nocluster' mount is introduced by Gang and I think it has real
>>>> user scenarios. I am curious about since node 0 is commonly used in
>>>> o2cb, why there is no any bug report before.
>>>> So let's try to fix the regression first.
>>> Real user case doesn’t mean this has to been done through kernel? This sounds like doing something in kernel that is to workaround some issue that can be done from user space.
>>> I didn’t see a Reviewed-by for the patch, how did it get merged?
>> Gang had left SUSE for some time, and busy with his new job.
>> I have vague memory, he said this commit approved & merged directly by Andrew Morton.
>> Gang dedicated to contribute ocfs2 community many years, and set up his competence
>> to other maintainers & reviewers.
>>
>> If Junxiao dislike this feature, and don't want to fix it as a bug.
>> I am willing to file a patch.
> To fix, it’s not only the regression it causes, but also do something in mount.ocfs2 to check whether any node is mounting the volume before nocluster mount and also stop other nodes mounting before  nocluster mount is unmounted. That’s to simulate what fsck.ocfs2/mkfs.ocfs2 do. Without that guard, this feature just provides a new way for customer to corrupt their data. It’s just time some customer would do something bad and lost their data. 
> I will leave how to handle this to you and Joseph, we already reverted this patch.

Searched the maillist and find the original thread for reference:
https://lore.kernel.org/ocfs2-devel/CH2PR18MB32064CCD80FE98F03B82A816CFAC0@CH2PR18MB3206.namprd18.prod.outlook.com/

I suggest we leave nocluster mount as a special mode and make its logic
won't impact other mode like cluster or local mount.
Agree with Junxiao, we have to try our best to prevent data corruption
even mistakenly used by customer.

Thanks,
Joseph

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

  reply	other threads:[~2022-06-07  6:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06  2:08 [Ocfs2-devel] [PATCH] Revert "ocfs2: mount shared volume without ha stack" heming.zhao--- via Ocfs2-devel
2022-06-06  8:27 ` Heming Zhao via Ocfs2-devel
2022-06-06 16:15 ` Junxiao Bi via Ocfs2-devel
2022-06-06 23:50   ` heming.zhao--- via Ocfs2-devel
2022-06-07  0:32     ` Heming Zhao via Ocfs2-devel
2022-06-07  2:07     ` Joseph Qi via Ocfs2-devel
2022-06-07  2:21       ` Junxiao Bi via Ocfs2-devel
2022-06-07  2:38         ` heming.zhao--- via Ocfs2-devel
2022-06-07  3:06           ` Junxiao Bi via Ocfs2-devel
2022-06-07  6:31             ` Joseph Qi via Ocfs2-devel [this message]
2022-06-07  9:42               ` Heming Zhao via Ocfs2-devel
  -- strict thread matches above, loose matches on Subject: below --
2022-06-03 22:28 Junxiao Bi via Ocfs2-devel
2022-06-04  8:45 ` heming.zhao--- via Ocfs2-devel
2022-06-04 16:19   ` Junxiao Bi via Ocfs2-devel
2022-06-25 13:30     ` 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=6f72c61f-fae4-9fa3-bcd9-5aa3f03db6ac@linux.alibaba.com \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=heming.zhao@suse.com \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=junxiao.bi@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 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).