From: "Alexander A. Filippov" <a.filippov@yadro.com>
To: <openbmc@lists.ozlabs.org>
Subject: Re: Alternative to the filesystem overlay
Date: Fri, 16 Aug 2019 12:09:55 +0300 [thread overview]
Message-ID: <20190816090955.GA15986@bbwork.lan> (raw)
In-Reply-To: <efb47539225e57a0ab0138987287c230@linux.vnet.ibm.com>
On Thu, Aug 15, 2019 at 12:38:16PM -0500, Adriana Kobylak wrote:
> In OpenBMC we've been using an overlay to make the read-only filesystem (or
> part of it) writable. It hasn't come without its issues, like missing
> directories (openbmc/openbmc#3564) and various flavors of corruption
> (openbmc/openbmc#3578 and issues when adding files to /etc in the build
> causing files that had been previously modified on the bmc to become
> corrupted).
There is one more issue for the same type - openbmc/openbmc#3468.
And it can't be solved by the way you propose.
>
> An alternative would be to use a bind mount and manage the file merging by
> an OpenBMC app. Doing some experimentation, seems this solves the issues
> seen above. The way that it'd work would be:
> - The init script or initramfs would do an rsync from /etc to the bind mount
> destination directory in the read-write filesystem, skipping the contents of
> a list which would contain the files that have been modified in the BMC and
> should be preserved.
> - A new OpenBMC app would monitor /etc for changes via inotify for example,
> and if a file is modified, it'd add it to the "list".
>
> Considerations:
> - The /etc dir mainly being a configuration destination does not get
> modified often so the app that is watching the directory would not be
> triggered often.
> - The bind mount would duplicate the contents of etc although it's not much.
> If space is a concern, some exploration could be done to have the bind mount
> be a tmpfs and have the monitor app copy the modified files to the
> read-write filesystem instead of adding them to a list.
>
> Thoughts?
>
Most of these issues can be solved by the simple shell scripts. We could modify
the initramfs/init scenario to exec these scripts at the moment when ROFS and
RWFS have mounted but are not combined to OVERLAY yet.
Of course, this method doesn't prevent an occurrence of any new issues of this
type but brings an easy way to solve them.
--
Regards,
Alexander
next prev parent reply other threads:[~2019-08-16 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 17:38 Alternative to the filesystem overlay Adriana Kobylak
2019-08-15 18:43 ` Andrew Geissler
2019-08-16 9:09 ` Alexander A. Filippov [this message]
2019-08-20 18:00 ` William Kennington
2019-08-21 7:28 ` Alexander A. Filippov
2019-08-21 0:56 ` Terry Duncan
2019-08-21 7:09 ` Alexander A. Filippov
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=20190816090955.GA15986@bbwork.lan \
--to=a.filippov@yadro.com \
--cc=openbmc@lists.ozlabs.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.