From: Gael Donval <gael.donval@manchester.ac.uk>
To: "hsiangkao@linux.alibaba.com" <hsiangkao@linux.alibaba.com>,
"linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>
Subject: Re: mkfs.erofs fails (failed to build shared xattrs, err 61)
Date: Tue, 12 Mar 2024 16:15:31 +0000 [thread overview]
Message-ID: <3335bbeb92ee627c3db5a31a8d247fa8c972fc86.camel@manchester.ac.uk> (raw)
In-Reply-To: <1b57afc3-53e0-42d7-87aa-bddd1ceec10b@linux.alibaba.com>
> > If there is harm, mkfs.erofs should strip anything that it does not
> > support without producing an error.
> >
> > Either way, there should be no error. :)
>
> Fair enough, I think I will do this for erofs-utils 1.8, but I tend
> to consider unsupported xattr namespaces as warn messages, users
> could silence these with proper '-d' message levels.
I'm absolutely fine with that as long as mkfs.erofs goes through with
generating the FS (it does not generate anything right now) and returns
success to the shell.
Thanks a lot for your help,
Gaël
>
> Thanks,
> Gao Xiang
prev parent reply other threads:[~2024-03-12 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 9:57 mkfs.erofs fails (failed to build shared xattrs, err 61) Gael Donval
2024-03-12 10:44 ` Gao Xiang
2024-03-12 10:45 ` Gao Xiang
2024-03-12 11:07 ` Gael Donval
2024-03-12 11:37 ` Gao Xiang
2024-03-12 11:57 ` Gao Xiang
2024-03-12 12:01 ` Gael Donval
2024-03-12 12:43 ` Gao Xiang
2024-03-12 13:14 ` Gael Donval
2024-03-12 14:15 ` Gao Xiang
2024-03-12 15:29 ` Gael Donval
2024-03-12 15:39 ` Gao Xiang
2024-03-12 16:15 ` Gael Donval [this message]
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=3335bbeb92ee627c3db5a31a8d247fa8c972fc86.camel@manchester.ac.uk \
--to=gael.donval@manchester.ac.uk \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.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 read-only IMAP folder(s) and NNTP newsgroup(s).