From: Atom2 <ariel.atom2@web2web.at>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Xu Wang <xuw@redhat.com>, hujianyang <hujianyang@huawei.com>,
"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: stat inconsistency with overlayfs
Date: Tue, 03 Mar 2015 18:12:45 +0100 [thread overview]
Message-ID: <54F5EB8D.1080201@web2web.at> (raw)
In-Reply-To: <CAJfpegtV-UZmnu8HvH9RQiewv14bqpUao=OvnOCCJGhE0DXDHw@mail.gmail.com>
Mikolos,
thanks for joining the party.
Am 03.03.15 um 16:14 schrieb Miklos Szeredi:
> Atom2,
>
>> The use case behind that is to be able to backup only files from the
>> upperdir for several systems sharing a common lowerdir filesystem. I have
>> used that (scripted approach via rsync) now for quiet some time and a few
>> kernels back and it seemed to have worked very well.
>
> Why don't you just back up the upper directory itself instead of
> messing around with device numbers?
I am not aware of any such option, but if you could explain that a
little bit more in detail, I am happy to explore other options.
Just for everybody to be on the same page: In my use case the r/o
lowerdir's root directory is also the root of my file system (which is
shared across many systems) from which (all) the systems boot. Using an
initramfs during the boot process, the upperdir file system (which is
different per system) is then r/w overlay-mounted over the common r/o
lowerdir's root directory in order to catch any r/w access to the file
system.
So in essence and according to my understanding there's no direct access
to (only) the r/w upperdir (or only the lowerdir) from within any of the
running systems other than using the device field to see where a file
system entry actually exists - at least that's my current understanding.
But again, I am happy to learn ...
Regards Atom2
next prev parent reply other threads:[~2015-03-03 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 18:15 stat inconsistency with overlayfs Atom2
2015-02-26 5:25 ` hujianyang
2015-02-26 6:45 ` Xu Wang
2015-03-02 20:45 ` Atom2
2015-03-03 15:14 ` Miklos Szeredi
2015-03-03 17:12 ` Atom2 [this message]
2015-03-04 2:24 ` hujianyang
2015-03-04 11:06 ` Miklos Szeredi
2015-03-02 20:45 ` Atom2
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=54F5EB8D.1080201@web2web.at \
--to=ariel.atom2@web2web.at \
--cc=hujianyang@huawei.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=xuw@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.