mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Ahmet Eray Karadag <eraykrdg1@gmail.com>, ocfs2-devel@lists.linux.dev
Cc: Albin Babu Varghese <albinbabuvarghese20@gmail.com>,
	mark@fasheh.com, jlbec@evilplan.org,
	linux-kernel@vger.kernel.org, Heming Zhao <heming.zhao@suse.com>,
	david.hunter.linux@gmail.com, skhan@linuxfoundation.org,
	syzbot+b93b65ee321c97861072@syzkaller.appspotmail.com
Subject: Re: [RFC RFT PATCH] ocfs2: Mark inode bad upon validation failure during read
Date: Wed, 5 Nov 2025 09:40:11 +0800	[thread overview]
Message-ID: <cadde0fd-e99e-4306-b9c8-327822756a95@linux.alibaba.com> (raw)
In-Reply-To: <CAHxJ8O9Yci6QzGckrsWhuoDHatYyOOok++ySmYc43WbEhFy3xg@mail.gmail.com>



On 2025/11/5 06:31, Ahmet Eray Karadag wrote:
> Hi folks,
> 
> I'm having some trouble getting xfstests-dev set up to test some ocfs2
> changes. I can't seem to get the configuration working correctly to run
> the ocfs2 test group.
> 
> Could anyone share some insights or pointers on the proper setup? Any
> help would be much appreciated.
> 
The basic steps is:
1. Configure a ocfs2 cluster, e.g:
$ cat /etc/ocfs2/cluster.conf
cluster:
        heartbeat_mode = local
        node_count = 1
        name = ocfs2cluster

node:
        number = 0
        cluster = ocfs2cluster
        ip_port = 7777
        ip_address = 127.0.0.1
        name = localhost

2. Online ocfs2 cluster:
$ /etc/init.d/o2cb.init online

3. Then run xfstests cases, e.g.:
$ ./check generic/001

Actually we prefer ocfs2tests to test ocfs2, which can be cloned at:
https://github.com/markfasheh/ocfs2-test

Thanks,
Joseph

  reply	other threads:[~2025-11-05  1:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 22:57 Ahmet Eray Karadag
2025-10-30  7:59 ` Heming Zhao
2025-10-30 22:07   ` Ahmet Eray Karadag
2025-10-31  2:30     ` Heming Zhao
2025-10-31  3:59       ` Albin Babu Varghese
2025-10-31  7:04         ` Heming Zhao
2025-10-31 13:54           ` Albin Babu Varghese
2025-10-31 14:05             ` Heming Zhao
2025-10-31 14:22               ` Albin Babu Varghese
2025-11-04 22:31                 ` Ahmet Eray Karadag
2025-11-05  1:40                   ` Joseph Qi [this message]
2025-10-31  7:10 ` Heming Zhao

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=cadde0fd-e99e-4306-b9c8-327822756a95@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=albinbabuvarghese20@gmail.com \
    --cc=david.hunter.linux@gmail.com \
    --cc=eraykrdg1@gmail.com \
    --cc=heming.zhao@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+b93b65ee321c97861072@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®