All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Gael Donval <gael.donval@manchester.ac.uk>,
	"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 19:37:33 +0800	[thread overview]
Message-ID: <25e533ad-e32c-419c-85c8-b8d4feb782a2@linux.alibaba.com> (raw)
In-Reply-To: <691120bfed626b78cc1107166f2fd964ca23ce99.camel@manchester.ac.uk>



On 2024/3/12 19:07, Gael Donval wrote:
>> On 2024/3/12 18:44, Gao Xiang wrote:
>>> Hi Gael,
>>>
>>> On 2024/3/12 17:57, Gael Donval wrote:
>>>> Dear list,
>>>>
>>>>      $ mkdir foo && touch foo/bar && mkfs.erofs foo.erofs.img foo
>>>>      mkfs.erofs 1.7.1
>>>>      <E> erofs: failed to build shared xattrs: [Error 61] No data
>>>> available
>>>>      <E> erofs:     Could not format the device : [Error 61] No
>>>> data available
>>>> That is at a location backed by BTRFS (btrfs-progs v6.7.1) on
>>>> kernel 6.8.0.
>>>>
>>>> If I use a TMPFS-supported folder instead all goes well.
>>>>
>>>>
>>>> Of course (NB "-x-1"),
>>>>
>>>>      $ mkdir foo && touch foo/bar && mkfs.erofs -x-1 foo.erofs.img
>>>> foo
>>>>
>>>> also works but is not how mkfs.erofs is meant to work in the
>>>> general case.
>>>
>>> Thanks for your feedback.
>>>
>>> Currently I don't have some BTRFS environment, I could set up one
>>> later.
>>> Yet in parallel could you provide a full message of
>>> "strace mkfs.erofs -x-1 foo.erofs.img foo" on BTRFS too?
>>
>> sorry, I meant "strace mkfs.erofs foo.erofs.img foo"
> 
> Hi,
> 
> Here it is.
> 

The problem here is that BTRFS could extract their internal
xattrs ("inode properties") in their own namespace which
don't belong to the original file itself like:

XATTR_BTRFS_PREFIX "compression" -> btrfs.compression = zstd

I think I need to introduce something to formally ignore
these xattrs like: `--xattrs-exclude=pattern`:
https://www.gnu.org/software/tar/manual/html_node/Extended-File-Attributes.html

Thanks,
Gao Xiang

> Thanks for your help,
> Gaël
> 
> 

  reply	other threads:[~2024-03-12 11:37 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 [this message]
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

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=25e533ad-e32c-419c-85c8-b8d4feb782a2@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=gael.donval@manchester.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.