gfs2 filesystem and dlm development
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
Cc: Alexander Aring <aahringo@redhat.com>,
	David Teigland <teigland@redhat.com>,
	gfs2@lists.linux.dev, ocfs2-devel@lists.linux.dev,
	Heming Zhao <heming.zhao@suse.com>
Subject: Re: ocfs2 mount error
Date: Mon, 11 Mar 2024 17:27:46 +0800	[thread overview]
Message-ID: <d3aea09b-3ad2-4f48-b86e-db46d3018bbd@linux.alibaba.com> (raw)
In-Reply-To: <Ze7IiZmlhRaOgdhm@valentin-vidic.from.hr>



On 3/11/24 5:02 PM, Valentin Vidić wrote:
> On Mon, Mar 11, 2024 at 04:37:39PM +0800, Joseph Qi wrote:
>> It seems that you are using fsdlm.
>> But from your running commands, I don't see how fsdlm get involved.
>> Could you please give more detail on how to reproduce it?
> 
> Sure, this is the original Pacemaker test script that failed:
> 
> https://salsa.debian.org/ha-team/ocfs2-tools/-/blob/master/debian/tests/pcmk?ref_type=heads
> 
> Basically it starts Corosync and DLM services and than calls:
> 
> mkfs.ocfs2
> fsck.ocfs2
> mount.ocfs2
> 

Thanks for quick reply.
Now it confirms that it is using fsdlm.

Joseph



  reply	other threads:[~2024-03-11  9:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 21:46 ocfs2 mount error Valentin Vidić
2024-03-11  8:37 ` Joseph Qi
2024-03-11  9:02   ` Valentin Vidić
2024-03-11  9:27     ` Joseph Qi [this message]
2024-03-11 12:28       ` Heming Zhao
2024-03-11 15:20     ` Alexander Aring
2024-03-11 19:27       ` Valentin Vidić
2024-03-11 23:43         ` Alexander Aring
2024-03-12  8:09           ` Valentin Vidić
2024-03-12 17:55             ` Alexander Aring
2024-03-12 18:37               ` Valentin Vidić
2024-03-12 19:55                 ` Alexander Aring
2024-03-12 20:03                   ` Alexander Aring
2024-03-12 20:42                   ` Valentin Vidić

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=d3aea09b-3ad2-4f48-b86e-db46d3018bbd@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=aahringo@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=heming.zhao@suse.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=teigland@redhat.com \
    --cc=vvidic@valentin-vidic.from.hr \
    /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