All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Mauro Condarelli <mc5686@mclink.it>,
	Amir Goldstein <amir73il@gmail.com>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	Mark Salyzyn <salyzyn@android.com>
Subject: Re: Frequent errors with OverlayFS on root
Date: Thu, 3 Sep 2020 09:09:26 -0400	[thread overview]
Message-ID: <20200903130926.GA9874@redhat.com> (raw)
In-Reply-To: <CAJfpegvFmHQmECkEq8Qffz-yaxPrKeabxftnYL8kExhhewyV1Q@mail.gmail.com>

On Thu, Sep 03, 2020 at 11:53:03AM +0200, Miklos Szeredi wrote:
> On Thu, Sep 3, 2020 at 11:24 AM Mauro Condarelli <mc5686@mclink.it> wrote:
> 
> > FYI: using OverlayFS this way and for this use-case was suggested
> > by SWUpdate maintainer (Stefano Babic) so I guess there are other
> > people relying on "correct" behavior around the world .
> 
> So my opinion is that this use case (modifying or even completely
> swapping out the lower layer while it is not mounted) should work
> perfectly fine with a "plain" configuration.
> 
> Doing this with redirect_dir, metacopy or index does sound somewhat
> scary and some of that obviously won't even work because of the broken
> origins.

Hi Miklos,

Shall we document that changing/swapping lower layers with existing
upper is not supported configuration with advanced features like
metacopy/redirect_dir/index.

This topic has come up now multiple times recently. It will be good
to make it very clear in documentation.

Thanks
Vivek


      reply	other threads:[~2020-09-03 14:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 17:46 Frequent errors with OverlayFS on root Mauro Condarelli
2020-09-01 18:43 ` Amir Goldstein
     [not found]   ` <2da4dd97-d7cb-ce1b-ada7-0152d65ce701@mclink.it>
2020-09-02  3:34     ` Amir Goldstein
2020-09-02 13:29       ` Vivek Goyal
2020-09-02 15:31         ` Amir Goldstein
2020-09-02 15:33         ` Mauro Condarelli
2020-09-02 20:20           ` Vivek Goyal
2020-09-03  7:25             ` Mauro Condarelli
2020-09-03  8:30               ` Amir Goldstein
2020-09-03  8:51                 ` Mauro Condarelli
2020-09-03  9:00                   ` Amir Goldstein
2020-09-03  9:01                     ` Amir Goldstein
2020-09-03  9:24                     ` Mauro Condarelli
2020-09-03  9:53                       ` Miklos Szeredi
2020-09-03 13:09                         ` Vivek Goyal [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=20200903130926.GA9874@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=mc5686@mclink.it \
    --cc=miklos@szeredi.hu \
    --cc=salyzyn@android.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.