From: Alexander Aring <aahringo@redhat.com>
To: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
Cc: Joseph Qi <joseph.qi@linux.alibaba.com>,
ocfs2-devel@oss.oracle.com, David Teigland <teigland@redhat.com>,
gfs2@lists.linux.dev, ocfs2-devel@lists.linux.dev
Subject: Re: ocfs2 mount error
Date: Mon, 11 Mar 2024 11:20:56 -0400 [thread overview]
Message-ID: <CAK-6q+jFv8tK4rF-xY6okTwhK87zMtOKP6fthzCQ-H8-4q=wbQ@mail.gmail.com> (raw)
In-Reply-To: <Ze7IiZmlhRaOgdhm@valentin-vidic.from.hr>
Hi,
On Mon, Mar 11, 2024 at 5:02 AM Valentin Vidić
<vvidic@valentin-vidic.from.hr> 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
when I try doing your steps (btw: thanks for sharing) to run
fsck.ocfs2 it tells me:
fsck.ocfs2: Unable to access cluster service while initializing the DLM
Looking into strace right before that I see a:
connect(4, {sa_family=AF_UNIX, sun_path=@"ocfs2_controld_sock"}, 22) =
-1 ECONNREFUSED (Connection refused)
it's true I don't have ocfs2_controld running, after looking into
ocfs2-tools source code, I declare it as not compilable with recent
corosync versions.
Maybe somebody else can help so I can try to reproduce it?
btw: a "trace-cmd stream -e dlm" would be nice to debug this issue.
After I look at your debugging information it would be nice to see if
the device() read for ast callbacks are there.
- Alex
next prev parent reply other threads:[~2024-03-11 15:21 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
2024-03-11 12:28 ` Heming Zhao
2024-03-11 15:20 ` Alexander Aring [this message]
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='CAK-6q+jFv8tK4rF-xY6okTwhK87zMtOKP6fthzCQ-H8-4q=wbQ@mail.gmail.com' \
--to=aahringo@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=joseph.qi@linux.alibaba.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=ocfs2-devel@oss.oracle.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).