From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: Alexander Aring <aahringo@redhat.com>
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 20:27:30 +0100 [thread overview]
Message-ID: <Ze9bIiT3rAWTtPJp@valentin-vidic.from.hr> (raw)
In-Reply-To: <CAK-6q+jFv8tK4rF-xY6okTwhK87zMtOKP6fthzCQ-H8-4q=wbQ@mail.gmail.com>
On Mon, Mar 11, 2024 at 11:20:56AM -0400, Alexander Aring wrote:
> 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.
Not sure about that, because I also don't have ocfs2_controld running.
This is ocfs2-tools v1.8.8 with corosync v3.1.7. Perhaps cluster stack
should be set with:
echo pcmk > /sys/fs/ocfs2/cluster_stack
> 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.
Here is a trace report for the fsck call:
cpus=1
fsck.ocfs2-1696 [000] 54.621075: dlm_lock_start: ls_id=2352585329 lkb_id=1 mode=PR flags=VALBLK res_name=2e39323539656662313866316162386331
fsck.ocfs2-1696 [000] 54.692487: dlm_lock_end: ls_id=2352585329 lkb_id=1 mode=PR flags=VALBLK error=0 res_name=2e39323539656662313866316162386331
fsck.ocfs2-1696 [000] 54.695447: dlm_ast: ls_id=2352585329 lkb_id=1 sb_flags= sb_status=0 res_name=2e39323539656662313866316162386331
fsck.ocfs2-1696 [000] 54.695636: dlm_lock_start: ls_id=2352585329 lkb_id=2 mode=EX flags=NOQUEUE|VALBLK res_name=53303030303030303030303030303030303030303030323030303030303030
fsck.ocfs2-1696 [000] 54.766959: dlm_lock_end: ls_id=2352585329 lkb_id=2 mode=EX flags=NOQUEUE|VALBLK error=0 res_name=53303030303030303030303030303030303030303030323030303030303030
fsck.ocfs2-1696 [000] 54.770765: dlm_ast: ls_id=2352585329 lkb_id=2 sb_flags= sb_status=0 res_name=53303030303030303030303030303030303030303030323030303030303030
fsck.ocfs2-1696 [000] 54.770821: dlm_lock_start: ls_id=2352585329 lkb_id=3 mode=EX flags=NOQUEUE|VALBLK res_name=4d303030303030303030303030303030303030303031383937333737316531
fsck.ocfs2-1696 [000] 54.845613: dlm_lock_end: ls_id=2352585329 lkb_id=3 mode=EX flags=NOQUEUE|VALBLK error=0 res_name=4d303030303030303030303030303030303030303031383937333737316531
fsck.ocfs2-1696 [000] 54.848395: dlm_ast: ls_id=2352585329 lkb_id=3 sb_flags= sb_status=0 res_name=4d303030303030303030303030303030303030303031383937333737316531
fsck.ocfs2-1696 [000] 54.868951: dlm_unlock_start: ls_id=2352585329 lkb_id=3 flags=VALBLK res_name=4d303030303030303030303030303030303030303031383937333737316531
fsck.ocfs2-1696 [000] 54.958319: dlm_unlock_end: ls_id=2352585329 lkb_id=3 flags=VALBLK error=0 res_name=4d303030303030303030303030303030303030303031383937333737316531
fsck.ocfs2-1696 [000] 54.982397: dlm_ast: ls_id=2352585329 lkb_id=3 sb_flags= sb_status=-65538 res_name=4d303030303030303030303030303030303030303031383937333737316531
fsck.ocfs2-1696 [000] 54.982450: dlm_lock_start: ls_id=2352585329 lkb_id=4 mode=EX flags=NOQUEUE|VALBLK res_name=4d303030303030303030303030303030303030303031393937333737316531
fsck.ocfs2-1696 [000] 55.056390: dlm_lock_end: ls_id=2352585329 lkb_id=4 mode=EX flags=NOQUEUE|VALBLK error=0 res_name=4d303030303030303030303030303030303030303031393937333737316531
fsck.ocfs2-1696 [000] 55.058946: dlm_ast: ls_id=2352585329 lkb_id=4 sb_flags= sb_status=0 res_name=4d303030303030303030303030303030303030303031393937333737316531
fsck.ocfs2-1696 [000] 55.082546: dlm_unlock_start: ls_id=2352585329 lkb_id=4 flags=VALBLK res_name=4d303030303030303030303030303030303030303031393937333737316531
fsck.ocfs2-1696 [000] 55.182903: dlm_unlock_end: ls_id=2352585329 lkb_id=4 flags=VALBLK error=0 res_name=4d303030303030303030303030303030303030303031393937333737316531
fsck.ocfs2-1696 [000] 55.210128: dlm_ast: ls_id=2352585329 lkb_id=4 sb_flags= sb_status=-65538 res_name=4d303030303030303030303030303030303030303031393937333737316531
fsck.ocfs2-1696 [000] 55.530687: dlm_unlock_start: ls_id=2352585329 lkb_id=2 flags=VALBLK res_name=53303030303030303030303030303030303030303030323030303030303030
fsck.ocfs2-1696 [000] 55.625015: dlm_unlock_end: ls_id=2352585329 lkb_id=2 flags=VALBLK error=0 res_name=53303030303030303030303030303030303030303030323030303030303030
fsck.ocfs2-1696 [000] 55.650054: dlm_ast: ls_id=2352585329 lkb_id=2 sb_flags= sb_status=-65538 res_name=53303030303030303030303030303030303030303030323030303030303030
fsck.ocfs2-1696 [000] 55.672033: dlm_unlock_start: ls_id=2352585329 lkb_id=1 flags=VALBLK res_name=2e39323539656662313866316162386331
fsck.ocfs2-1696 [000] 55.766844: dlm_unlock_end: ls_id=2352585329 lkb_id=1 flags=VALBLK error=0 res_name=2e39323539656662313866316162386331
fsck.ocfs2-1696 [000] 55.791829: dlm_ast: ls_id=2352585329 lkb_id=1 sb_flags= sb_status=-65538 res_name=2e39323539656662313866316162386331
--
Valentin
next prev parent reply other threads:[~2024-03-11 19: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
2024-03-11 12:28 ` Heming Zhao
2024-03-11 15:20 ` Alexander Aring
2024-03-11 19:27 ` Valentin Vidić [this message]
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=Ze9bIiT3rAWTtPJp@valentin-vidic.from.hr \
--to=vvidic@valentin-vidic.from.hr \
--cc=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 \
/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