From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "frank.li@vivo.com" <frank.li@vivo.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"brauner@kernel.org" <brauner@kernel.org>,
"slava@dubeyko.com" <slava@dubeyko.com>
Subject: Re: 回复: 回复: HFS/HFS+ maintainership action items
Date: Fri, 25 Apr 2025 18:25:58 +0000 [thread overview]
Message-ID: <d35a7b6e8fce1e894e74133d7e2fbe0461c2d0a5.camel@ibm.com> (raw)
In-Reply-To: <SEZPR06MB5269CBE385E73704B368001AE8842@SEZPR06MB5269.apcprd06.prod.outlook.com>
On Fri, 2025-04-25 at 11:39 +0000, 李扬韬 wrote:
> Hi Adrian,
>
> > Would you guys mind help me create an xfstest test environment as well?
>
> I am currently running arch linux on wsl 2 in a windows laptop.
>
> I'm following the README steps here (ing, not sure if I'll run into problems).
>
> https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/README?h=for-next
> git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
>
> Maybe slava and some other additions too?
Yes, I used this way to prepare the xfstests environment. So, the main steps:
(1) Clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
(2) Install all necessary packages + hfsprog tools. This step could depends from
a particular environment.
(3) Do make and make install. Usually, it works well but last time I had some
issues that I managed to resolve.
(4) Prepare the local.config file:
HFS case:
export TEST_DEV=/dev/sda1
export TEST_DIR=/mnt/test
export SCRATCH_DEV=/dev/sda2
export SCRATCH_MNT=/mnt/scratch
export FSTYP=hfs
HFS+ case:
export TEST_DEV=/dev/sda1
export TEST_DIR=/mnt/test
export SCRATCH_DEV=/dev/sda2
export SCRATCH_MNT=/mnt/scratch
export FSTYP=hfsplus
(5) Run the check command:
Group test (for example quick group):
sudo ./check -g quick
Particular test:
sudo ./check generic/001
Mostly, these steps should prepare the xfstests environment. Of course, it could
run on physical machine or inside of virtual machine. It needs to prepare the
two partitions or drives (test and scratch) for testing.
If you will have some troubles, please, let me know and I will try to help. :)
Thanks,
Slava.
next prev parent reply other threads:[~2025-04-25 18:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 21:52 HFS/HFS+ maintainership action items Viacheslav Dubeyko
2025-04-22 2:43 ` Theodore Ts'o
2025-04-22 4:16 ` Darrick J. Wong
2025-04-22 7:21 ` John Paul Adrian Glaubitz
2025-04-22 7:20 ` John Paul Adrian Glaubitz
2025-04-22 12:35 ` John Paul Adrian Glaubitz
2025-04-22 21:12 ` Viacheslav Dubeyko
2025-04-22 21:47 ` John Paul Adrian Glaubitz
2025-04-22 21:48 ` John Paul Adrian Glaubitz
2025-04-25 1:06 ` Viacheslav Dubeyko
2025-04-25 10:17 ` 回复: " 李扬韬
2025-04-25 11:32 ` John Paul Adrian Glaubitz
2025-04-25 11:39 ` 回复: " 李扬韬
2025-04-25 18:25 ` Viacheslav Dubeyko [this message]
2025-04-25 19:36 ` 回复: " 李扬韬
2025-04-25 19:44 ` Viacheslav Dubeyko
2025-04-26 6:17 ` 回复: " 李扬韬
2025-04-26 6:59 ` John Paul Adrian Glaubitz
2025-04-27 20:28 ` Viacheslav Dubeyko
2025-05-02 3:01 ` Theodore Ts'o
2025-05-02 19:14 ` Viacheslav Dubeyko
2025-05-03 5:39 ` Theodore Ts'o
2025-05-05 23:08 ` Viacheslav Dubeyko
2025-04-25 20:51 ` John Paul Adrian Glaubitz
2025-04-25 18:02 ` Viacheslav Dubeyko
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=d35a7b6e8fce1e894e74133d7e2fbe0461c2d0a5.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=brauner@kernel.org \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.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 NNTP newsgroup(s).