From: Miklos Szeredi <miklos@szeredi.hu>
To: Jan Olszak <j.olszak@samsung.com>
Cc: David Howells <dhowells@redhat.com>,
"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: Optional switching off cow in overlayfs
Date: Mon, 22 Jun 2015 15:53:54 +0200 [thread overview]
Message-ID: <CAJfpegsVqzVhq8BjCwqA+6dEZey0aNb4amnnOT_JVDfzki9v1g@mail.gmail.com> (raw)
In-Reply-To: <5588116E.20509@samsung.com>
On Mon, Jun 22, 2015 at 3:45 PM, Jan Olszak <j.olszak@samsung.com> wrote:
> The lower fs is most likely ext4.
> Unfortunately making a file immutable won't solve the problem. There's
> nothing wrong in modifying the file and it should stay possible.
>
> I just want to switch off copy on write for some files. Can you see another
> way?
Ah, you want to allow modification of file on the lower layer?
You can bind mount individual files from the lower layer to the
overlay. That fixes the "allow modification" part. But what should
happen on rename or unlink?
Thanks,
Miklos
next prev parent reply other threads:[~2015-06-22 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 13:25 Optional switching off cow in overlayfs Jan Olszak
2015-06-18 13:39 ` David Howells
2015-06-18 14:43 ` Jan Olszak
2015-06-22 11:32 ` Miklos Szeredi
2015-06-22 13:45 ` Jan Olszak
2015-06-22 13:53 ` Miklos Szeredi [this message]
2015-06-22 14:26 ` Jan Olszak
2015-06-22 14:37 ` Miklos Szeredi
2015-06-22 15:32 ` Jan Olszak
2015-06-23 9:27 ` David Howells
2015-06-23 10:36 ` Jan Olszak
2015-06-23 13:23 ` David Howells
2015-06-23 16:05 ` Jan Olszak
2015-06-23 16:07 ` Jan Olszak
2015-06-24 16:03 ` Jan Olszak
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=CAJfpegsVqzVhq8BjCwqA+6dEZey0aNb4amnnOT_JVDfzki9v1g@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=dhowells@redhat.com \
--cc=j.olszak@samsung.com \
--cc=linux-unionfs@vger.kernel.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.
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.