From: Christoph Hellwig <hch@infradead.org>
To: Auke Kok <auke.kok@versity.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] common: add scoutfs support.
Date: Sun, 29 Jun 2025 22:38:55 -0700 [thread overview]
Message-ID: <aGIi7wHaq7cPMiZU@infradead.org> (raw)
In-Reply-To: <20250627184220.114746-1-auke.kok@versity.com>
On Fri, Jun 27, 2025 at 11:42:20AM -0700, Auke Kok wrote:
> Basic scoutfs support: scoutfs uses 2 devices for a filesystem, one for
> metadata, and one for data. This requires that we pass a metadev_path
> argument to every mount call, as well as a quorum_slot option.
>
> To run any of these tests on scoutfs, you'll need to build and
> install the out-of-tree kernel module `scoutfs.ko`, and the `scoutfs`
> userspace utility, which can `mkfs` a scoutfs filesystem. The tests
> themselves are unmodified - many of them will be skipped due to
> unsupported features.
xfstests is only really intended to test in-tree file systems, or at
least those submitted upstream for inclusion and still in-progress.
next prev parent reply other threads:[~2025-06-30 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 18:42 [PATCH] common: add scoutfs support Auke Kok
2025-06-30 5:38 ` Christoph Hellwig [this message]
2025-06-30 18:16 ` Auke Kok
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=aGIi7wHaq7cPMiZU@infradead.org \
--to=hch@infradead.org \
--cc=auke.kok@versity.com \
--cc=fstests@vger.kernel.org \
/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