All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>, Vivek Goyal <vgoyal@redhat.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"Maciej Zięba" <maciekz82@gmail.com>,
	"Theodore Tso" <tytso@mit.edu>
Subject: Re: overlayfs 4.19: unable to make backup link: Invalid cross-device link
Date: Wed, 14 Nov 2018 11:46:59 +0200	[thread overview]
Message-ID: <CAOQ4uxjsfgfo3rXtFKQk4A_fU2tvo38GFhzz7H9h1+R4trjd6Q@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxiu6iS-VuEtPhequVp7Ukx7Kh0FUpECSXfkaZN==o7sJw@mail.gmail.com>

On Tue, Oct 30, 2018 at 6:44 AM Amir Goldstein <amir73il@gmail.com> wrote:
>
...
>
> So let's try to bisect the offending feature first.
> If we can't find an offending feature, then there may be an offending
> commit in 4.18..4.19
>
> With kernel 4.19, please try to reproduce after:
> echo N > /sys/module/overlay/parameters/metacopy
> and then after:

Miklos, Vivek,

FYI, Maciej has reported that he reproduced the same issue and that
disabling metacopy fixes the problem.

He offered to provide more information if requested.

Thanks,
Amir.

  reply	other threads:[~2018-11-14  9:46 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
2018-10-30  4:44     ` Amir Goldstein
2018-11-14  9:46       ` Amir Goldstein [this message]
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=CAOQ4uxjsfgfo3rXtFKQk4A_fU2tvo38GFhzz7H9h1+R4trjd6Q@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=maciekz82@gmail.com \
    --cc=miklos@szeredi.hu \
    --cc=tytso@mit.edu \
    --cc=vgoyal@redhat.com \
    /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.