From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>,
Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: Building image fails on btrfs due to mkfs.erofs xattr limitation
Date: Sat, 05 Jul 2025 21:55:04 +0200 [thread overview]
Message-ID: <871pqu5s6f.fsf@alyssa.is> (raw)
In-Reply-To: <990a7393-185f-4b6c-b4ee-57a4aae17dd8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> On 7/5/25 04:52, Alyssa Ross wrote:
>> Demi Marie Obenour <demiobenour@gmail.com> writes:
>>
>>> Unless extended attributes are disabled (with -x-1), mkfs.erofs
>>> fails when the source is a BTRFS filesystem. This prevents the
>>> Spectrum image from being built. Using -x-1 seems to produce a
>>> working installer, though I only smoke tested it (by trying the
>>> example VMs).
>>
>> That's odd — I frequently run mkfs.erofs on btrfs. Could it be some
>> difference in our filesystem/mount options? Could it just be that my
>> files don't have extended attributes and yours do (SELinux)?
>
> Yeah, it might well be SELinux. Spectrum should still build on
> systems with SELinux enabled, though. Does Spectrum use extended
> attributes? If not, would it make sense to disable them with -x-1?
> In the future, SELinux on the host will require fixing this, but
> for now it's better to fix the build error.
Yes, of course. I just wanted to understand why it might be happening
for you and not to me. Disabling extended attributes in mkfs.erofs
sounds like the right thing to do.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2025-07-05 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 2:02 Building image fails on btrfs due to mkfs.erofs xattr limitation Demi Marie Obenour
2025-07-05 8:52 ` Alyssa Ross
2025-07-05 15:11 ` Demi Marie Obenour
2025-07-05 19:55 ` Alyssa Ross [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=871pqu5s6f.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).