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 21:42:54 +0100 [thread overview]
Message-ID: <ZfC-TjBz9xBIqZb-@valentin-vidic.from.hr> (raw)
In-Reply-To: <CAK-6q+iWzE_QgH3sYK6v8JS+p9KxaEGihoe-6WD1-pfz964bCw@mail.gmail.com> <CAK-6q+j8Ag5yj6pn0P4wC2kRSNMVaHGmVY+G6+H5aYD1-ygzSw@mail.gmail.com>
On Tue, Mar 12, 2024 at 03:55:46PM -0400, Alexander Aring wrote:
> Then you can reply to the mail with:
>
> Tested-by: Valentin Vidić <vvidic@valentin-vidic.from.hr>
>
> that would help to bring the fix upstream.
Sure, replied to the other thread.
> I see, I currently have plans/ideas to add namespace support into
> kernel DLM that might help you by extending your testing. The general
> idea would be that you can do something like:
>
> ...
> ip netns exec node1 mount /dev/fake_shared_block /mnt/node1
> ip netns exec node2 mount /dev/fake_shared_block /mnt/node2
> ip netns exec node3 mount /dev/fake_shared_block /mnt/node3
> ...
Yeah, that would definitely be cool. And thanks for the pointers,
I will definitely try to use namespaces for some simpler corosync
tests first.
> It also requires a ocfs2-tools tool at a specific location:
>
> /sbin/ocfs2_hb_ctl
>
> maybe this is your issue why it wasn't working. My kernel was
> complaining about it because it was missing in /sbin/
That binary is already in the Debian package. I think the error
fsck reported was something like "Could not create domain".
--
Valentin
prev parent reply other threads:[~2024-03-12 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Ze4qSvzGJDt5yxC3@valentin-vidic.from.hr>
2024-03-11 8:37 ` ocfs2 mount error 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ć
2024-03-12 19:55 ` Alexander Aring
2024-03-12 20:03 ` Alexander Aring
2024-03-12 20:42 ` Valentin Vidić [this message]
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=ZfC-TjBz9xBIqZb-@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).