From: Ralph Sennhauser <ralph.sennhauser@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
LEDE Development List <lede-dev@lists.infradead.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Christoph Hellwig <hch@infradead.org>,
openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] [RFC] Pre-seeded files/directories for UBIFS
Date: Sat, 20 May 2017 23:04:19 +0200 [thread overview]
Message-ID: <20170520230419.30d4e496@gmail.com> (raw)
In-Reply-To: <aa843f51-b037-5a09-28f4-f0b7b5396ce5@nod.at>
Hi Richard,
On Sat, 20 May 2017 21:57:36 +0200
Richard Weinberger <richard@nod.at> wrote:
> Ralph,
>
> Am 20.05.2017 um 21:36 schrieb Ralph Sennhauser:
> >>> These days I had an interesting discussion with Christoph about
> >>> overlayfs and its burden. The main use-case of overlayfs in
> >>> combination with UBIFS is having a squashfs as lower and UBIFS as
> >>> upper directory. Such that all changes to the read-only squashfs
> >>> go into UBIFS. Upon a factory reset all files within the UBIFS
> >>> will be removed and the merged directory is clean again.
> >>> Christoph argued that such a functionality could be achieved
> >>> without overlayfs if the filesystem supported something like
> >>> pre-seeded files or directories. This would lower memory
> >>> pressure and complexity.
> >>
> >> As you may know, OpenWrt/LEDE have been using this scheme for many
> >> years now (before it was named overlayfs, this was called mini
> >> fanout overlay ~10 yrs ago) with squashfs + jffs2 before on P-NOR
> >> flashes. There are still devices like those that benefit from
> >> squashfs(ro)+jffs2(rw), so while bringing a similar functionality
> >> using UBIFS exclusively would be interesting, it would still make
> >> Linux distribution want to support a more generic scheme which is
> >> using overlayfs as well.
> >>
> >
> > There is also the size consideration. Unless a seeded ubifs can get
> > close to squashfs in terms of compression there would still be a
> > use-case for squashfs with an ubifs overlay. My current root as
> > ubifs instead of squashfs is 76.8% bigger.
>
> You seem to misunderstand this feature, the goal is not to void all
> uses of squashfs.
> I'm pretty sure for the LEDE usecase squashfs is the better choice.
Probably depends on the device but is beyond the point. Just wanted to
mention in response to the main point being the factory reset of the
squashfs + ubifs overlay setup that size is just as important or even
more important at least for some.
Whether you want to implement and maintain another solution to the
factory reset problem in ubifs which falls short of full snapshot
support is up to you.
Ralph
next prev parent reply other threads:[~2017-05-20 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 16:12 [RFC] Pre-seeded files/directories for UBIFS Richard Weinberger
2017-05-20 18:39 ` Florian Fainelli
2017-05-20 18:48 ` Richard Weinberger
2017-05-20 19:36 ` [OpenWrt-Devel] " Ralph Sennhauser
2017-05-20 19:57 ` Richard Weinberger
2017-05-20 21:04 ` Ralph Sennhauser [this message]
2017-05-21 8:37 ` Geert Uytterhoeven
2017-05-21 8:40 ` Richard Weinberger
2017-05-21 12:23 ` Ralph Sennhauser
2017-05-21 15:38 ` Richard Weinberger
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=20170520230419.30d4e496@gmail.com \
--to=ralph.sennhauser@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=hch@infradead.org \
--cc=lede-dev@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=richard@nod.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox