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 19:44:01 +0000 [thread overview]
Message-ID: <97cd591a7b5a2f8e544f0c00aeea98cd88f19349.camel@ibm.com> (raw)
In-Reply-To: <SEZPR06MB5269BB960025304C687D6270E8842@SEZPR06MB5269.apcprd06.prod.outlook.com>
Hi Yangtao,
On Fri, 2025-04-25 at 19:36 +0000, 李扬韬 wrote:
> Hi Slava,
>
> > If you will have some troubles, please, let me know and I will try to help. :)
>
> There are some strange issues indeed,. : )
>
> One has been solved, and the other may be solved by changing the environment.
>
> 1). Header files installed, but linux/blkdev.h is still missing.
>
> Currently I copied the header files manually and it works.
>
> /usr/include/liburing/compat.h:11:10: fatal error: linux/blkdev.h: No such file or directory
> 11 | #include <linux/blkdev.h>
> | ^~~~~~~~~~~~~~~~
> compilation terminated.
> make[3]: *** [Makefile:51: fsstress] Error 1
> make[2]: *** [include/buildrules:31: ltp] Error 2
> make[1]: *** [Makefile:65: default] Error 2
> make: *** [Makefile:63: default] Error 2
>
Do you have libblkid-dev installed?
> 2). Arch Linux has the hfsprogs installation package, but after installation there is only mkfs.hfsplus, missing mkfs.hfs
>
As far as I know, you need to use -h option to create HFS volume:
usage: mkfs.hfsplus [-N [partition-size]] [hfsplus-options] special-device
options:
-h create an HFS format filesystem (HFS Plus is the default)
-N do not create file system, just print out parameters
-s use case-sensitive filenames (default is case-insensitive)
-w add a HFS wrapper (i.e. Native Mac OS 9 bootable)
where hfsplus-options are:
-J [journal-size] make this HFS+ volume journaled
-D journal-dev use 'journal-dev' for an external journal
-G group-id (for root directory)
-U user-id (for root directory)
-M octal access-mask (for root directory)
-b allocation block size (4096 optimal)
-c clump size list (comma separated)
a=blocks (attributes file)
b=blocks (bitmap file)
c=blocks (catalog file)
d=blocks (user data fork)
e=blocks (extents file)
r=blocks (user resource fork)
-i starting catalog node id
-n b-tree node size list (comma separated)
e=size (extents b-tree)
c=size (catalog b-tree)
a=size (attributes b-tree)
-v volume name (in ascii or UTF-8)
examples:
mkfs.hfsplus -v Untitled /dev/rdisk0s7
mkfs.hfsplus -v Untitled -n c=4096,e=1024 /dev/rdisk0s7
mkfs.hfsplus -v Untitled -c b=64,c=1024 /dev/rdisk0s7
> I think if I switch to Ubuntu or something, this problem should go away.
>
> I used the following command to test and got these failure cases.
>
> sudo ./check -g quick
>
> Failures: generic/001 generic/002 generic/003 generic/005 generic/006 generic/007 generic/011 generic/013 generic/020 generic/023 generic/024 generic/028 generic/029 generic/030 generic/035 generic/037 generic/062 generic/067 generic/069 generic/070 generic/075 generic/076 generic/079 generic/080 generic/084 generic/087 generic/088 generic/091 generic/095 generic/097 generic/098 generic/112 generic/113 generic/117 generic/120 generic/124 generic/126 generic/131 generic/135 generic/141 generic/169 generic/184 generic/198 generic/207 generic/210 generic/211 generic/212 generic/215 generic/221 generic/236 generic/245 generic/246 generic/247 generic/248 generic/249 generic/257 generic/258 generic/263 generic/294 generic/306 generic/308 generic/309 generic/313 generic/337 generic/338 generic/346 generic/360 generic/362 generic/364 generic/366 generic/377 generic/393 generic/394 generic/401 generic/403 generic/406 generic/409 generic/410 generic/411 generic/412 generic/423 generic/424 generic/428 generic/437 generic/441 generic/443 generic/448 generic/450 generic/451 generic/452 generic/460 generic/465 generic/471 generic/472 generic/478 generic/484 generic/486 generic/490 generic/504 generic/519 generic/523 generic/524 generic/525 generic/528 generic/532 generic/533 generic/538 generic/545 generic/555 generic/571 generic/591 generic/604 generic/609 generic/611 generic/615 generic/618 generic/632 generic/634 generic/636 generic/637 generic/638 generic/639 generic/647 generic/676 generic/706 generic/708 generic/728 generic/729 generic/732 generic/736 generic/740 generic/755 generic/759 generic/760 generic/761 generic/763
> Failed 136 of 614 tests
>
Yeah, it is reproducible.
Thanks,
Slava.
next prev parent reply other threads:[~2025-04-25 19:44 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
2025-04-25 19:36 ` 回复: " 李扬韬
2025-04-25 19:44 ` Viacheslav Dubeyko [this message]
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=97cd591a7b5a2f8e544f0c00aeea98cd88f19349.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).