Re: [PATCH 0/7] overlay filesystem: request for inclusion

[Andrew Morton]

On Thu, 09 Jun 2011 14:47:49 +0200
Miklos Szeredi <miklos@xxxxxxxxxx> wrote:

> Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> writes:
> 
> > On Thu, 9 Jun 2011 11:59:34 +1000 NeilBrown <neilb@xxxxxxx> wrote:
> >
> >> On Wed, 8 Jun 2011 15:32:08 -0700 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
> >> wrote:
> >> > I've never really understood the need for fs overlaying.  Who wants it?
> >> > What are the use-cases?
> >> 
> >> https://lwn.net/Articles/324291/
> >> 
> >> I think the strongest use case is that LIVE-DVD's want it to have a
> >> write-able root filesystem which is stored on the DVD.
> >
> > Well, these things have been around for over 20 years.  What motivated
> > the developers of other OS's to develop these things and how are their
> > users using them?
> 
> That's a good question, Erez might be able to answer that better.
> 
> We have customers who need this for the "common base + writable
> configuration" case in a virtualized environment.
> 
> Since overlayfs's announcement several projects have tried it and have
> been very good testers and bug reporters.  These include OpenWRT, Ubuntu
> and other Debian based live systems.

I assume that the live CD was your motivator for developing overlayfs?

> >> > This sort of thing could be implemented in userspace and wired up via
> >> > fuse, I assume.  Has that been attempted and why is it inadequate?
> 
> Yes, unionfs-fuse and deltafs (written by me) are two examples.
> 
> One issue that a customer had with deltafs was lack of XIP support.  The
> other one (from the same customer) was the general yuck factor of
> userspace filesystems.
> 
> There are also performance and resource use issues associated with
> userspace filesystems.  These may or may not be problem depending on the
> actual use.  But it's a fact that out-of-kernel filesystems will never
> be as efficient as in-kernel ones.

Yes, userspace filesystems have a good yuck factor.  In a way it's a
sad commentary on the concept of FUSE, but I guess one could look at it
another way: FUSE is good for prototypes and oddball small-volume stuff
but once a FUSE-based setup has proven useful and people are getting
benefit from it, it's time to look at an in-kernel implementation.

> > Another issue: there have been numerous attempts at Linux overlay
> > filesystems from numerous parties.  Does (or will) this implementation
> > satisfy all their requirements?
> 
> Overlayfs aims to be the simplest possible but not simpler.
> 
> I think the reason why "aufs" never had a real chance at getting merged
> is because of feature creep.
> 
> Of course I expect new features to be added to overlayfs after the
> merge, but I beleive some of the features in those other solutions are
> simply unnecessary.

This is my main worry.  If overlayfs doesn't appreciably decrease the
motivation to merge other unioned filesystems then we might end up with
two similar-looking things.  And, I assume, the later and more
fully-blown implementation might make overlayfs obsolete but by that
time it will be hard to remove.

So it would be interesting to hear the thoughts of the people who have
been working on the other implementations.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/