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: Tue, 12 Mar 2024 19:37:30 +0100 [thread overview]
Message-ID: <ZfCg6o3Kmkq78SIG@valentin-vidic.from.hr> (raw)
In-Reply-To: <CAK-6q+hBa08LoAEhsdiiG4DarCGF-CWy41zDjU3zB81P7hHx1A@mail.gmail.com>
On Tue, Mar 12, 2024 at 01:55:54PM -0400, Alexander Aring wrote:
> I was able to reproduce the issue and sent a fix out.
Yay, thanks a lot for testing, I can confirm the patches fix the problem
for me!
> If you want to extend your debian testing using different approach
> (not libdlm) this can be done by:
>
> mount -t ocfs2_dlmfs none /dlm
I tried that but fsck than fails to make a lock, so I think ocfs2_dlmfs
is only relevant when used with o2cb cluster type instead of corosync.
> I am curious about your testing at debian cluster, do you also test gfs2?
Yes, a similar test for gfs2 would be this:
https://salsa.debian.org/ha-team/gfs2-utils/-/blob/master/debian/tests/corosync?ref_type=heads
It is not really a cluster test since it only runs on one KVM
machine. But as a package test it works well because even for
1-node cluster all the code (userspace and kernel) still needs
to work correctly.
--
Valentin
next prev parent reply other threads:[~2024-03-12 18:37 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ć
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ć [this message]
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=ZfCg6o3Kmkq78SIG@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