From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"frank.li@vivo.com" <frank.li@vivo.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: RE: [HFS] generic/740 failure details
Date: Fri, 6 Jun 2025 17:52:39 +0000 [thread overview]
Message-ID: <33619f01e6d14d54b1f49890ff25e771db2fcedf.camel@ibm.com> (raw)
In-Reply-To: <7d3c595141e8ce70e0dd4b0b6fe28bfc7649bd2b.camel@physik.fu-berlin.de>
Hi Adrian,
On Fri, 2025-06-06 at 08:31 +0200, John Paul Adrian Glaubitz wrote:
> Hi Slava,
>
> On Thu, 2025-06-05 at 22:41 +0000, Viacheslav Dubeyko wrote:
> > It looks like we need to modify the HFS/HFS+ mkfs tool to refuse the reformat of
> > existing file system and to add the forcing option.
> >
> > Adrian, How does it feasible such modification?
>
> It would be certainly possible although we would deviate from what Apple
> does upstream with their hfs utilities. I'll add an issue in my repository
> for hfs for Linux [1].
>
Could we suggest this option for Apple's repository? Or is HFS tool's code
already obsolete for Apple?
Anyway, we need to have this option. Otherwise, it's too easy to destroy the
existing file system by mistake.
Feel free to assign [1,2] issues for yourself. :)
Thanks,
Slava.
> Adrian
>
> > [1] https://github.com/glaubitz/hfs/tree/linux
[1] https://github.com/hfs-linux-kernel/hfs-linux-kernel/issues/74
[2] https://github.com/hfs-linux-kernel/hfs-linux-kernel/issues/215
next prev parent reply other threads:[~2025-06-06 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 22:41 [HFS] generic/740 failure details Viacheslav Dubeyko
2025-06-06 6:31 ` John Paul Adrian Glaubitz
2025-06-06 17:52 ` Viacheslav Dubeyko [this message]
2025-06-09 10:52 ` Yangtao Li
2025-06-09 19:41 ` Viacheslav Dubeyko
2025-06-10 5:43 ` John Paul Adrian Glaubitz
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=33619f01e6d14d54b1f49890ff25e771db2fcedf.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).