From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: overlayfs <linux-unionfs@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: overlayfs 4.19: unable to make backup link: Invalid cross-device link
Date: Mon, 29 Oct 2018 18:04:04 -0400 [thread overview]
Message-ID: <20181029220404.GB15839@thunk.org> (raw)
In-Reply-To: <CAJfpegtCYkXiSYtw4dWGc=Fj2U3GaWiOiub+JmZ8pRXHNk4ERQ@mail.gmail.com>
On Mon, Oct 29, 2018 at 09:31:58AM +0100, Miklos Szeredi wrote:
> Can you please post
>
> grep OVERLAY_FS .config
Sure, here you go:
% zgrep OVERLAY_FS /proc/config.gz
CONFIG_OVERLAY_FS=m
CONFIG_OVERLAY_FS_REDIRECT_DIR=y
CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW=y
CONFIG_OVERLAY_FS_INDEX=y
# CONFIG_OVERLAY_FS_XINO_AUTO is not set
CONFIG_OVERLAY_FS_METACOPY=y
And this was the config on the working 4.18 kernel:
% grep OVERLAY_FS /boot/config-4.18.0-2-amd64
CONFIG_OVERLAY_FS=m
# CONFIG_OVERLAY_FS_REDIRECT_DIR is not set
CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW=y
# CONFIG_OVERLAY_FS_INDEX is not set
# CONFIG_OVERLAY_FS_XINO_AUTO is not set
The underlying file system is ext4.
Thanks!
- Ted
next prev parent reply other threads:[~2018-10-29 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 20:04 overlayfs 4.19: unable to make backup link: Invalid cross-device link Theodore Y. Ts'o
2018-10-29 7:37 ` Amir Goldstein
2018-10-29 8:31 ` Miklos Szeredi
2018-10-29 22:04 ` Theodore Y. Ts'o [this message]
2018-10-30 4:44 ` Amir Goldstein
2018-11-14 9:46 ` Amir Goldstein
2018-11-14 9:55 ` Miklos Szeredi
2018-11-14 10:28 ` Maciej Zięba
2018-11-14 10:33 ` Maciej Zięba
2018-11-14 12:09 ` Amir Goldstein
2018-11-14 12:14 ` Maciej Zięba
2018-11-14 14:25 ` Vivek Goyal
2018-11-14 18:40 ` Maciej Zięba
2018-11-14 21:33 ` Maciej Zięba
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=20181029220404.GB15839@thunk.org \
--to=tytso@mit.edu \
--cc=linux-fsdevel@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 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.