From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: btrfs+overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off.
Date: Sat, 10 Apr 2021 14:03:21 -0600 [thread overview]
Message-ID: <CAJCQCtSC36c5yNo+H2sy0o1f+XerjDSj-KYxPZS4GX6v5czUgw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQDyOh-EWL2QMMgNQeY6KDpHqducVRpn_63O30KuX2diQ@mail.gmail.com>
Keeping everything else the same, and only reverting to kernel
5.9.16-200.fc33.x86_64, this kernel message
>overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off
no longer appears when I 'podman system reset' or when 'podman build'
bolt, using the overlay driver.
However, I do still get
Bail out! ERROR:../tests/test-common.c:1413:test_io_dir_is_empty:
'empty' should be FALSE
--
Chris Murphy
next prev parent reply other threads:[~2021-04-10 20:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 22:03 btrfs+overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off Chris Murphy
2021-04-10 8:03 ` Amir Goldstein
2021-04-10 17:36 ` Chris Murphy
2021-04-10 17:55 ` Amir Goldstein
2021-04-10 19:36 ` Chris Murphy
2021-04-10 19:42 ` Chris Murphy
2021-04-10 19:43 ` Chris Murphy
2021-04-10 19:44 ` Chris Murphy
2021-04-10 20:03 ` Chris Murphy [this message]
2021-04-11 5:12 ` Amir Goldstein
2021-04-11 6:05 ` Chris Murphy
2021-04-11 7:28 ` Amir Goldstein
2021-04-13 21:50 ` Chris Murphy
2021-04-12 8:41 ` Miklos Szeredi
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=CAJCQCtSC36c5yNo+H2sy0o1f+XerjDSj-KYxPZS4GX6v5czUgw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=amir73il@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).