Re: [PATCH 14/39] union-mount: Union mounts documentation

From: Valerie Aurora
Date: Wed Aug 18 2010 - 14:56:08 EST


On Wed, Aug 18, 2010 at 10:23:52AM +0900, J. R. Okajima wrote:
>
> Valerie Aurora:
> > and at least three national lab computer clusters. The best argument
> > for their need for a union file system is that they are using unionfs
> > and aufs despite the pain of using out-of-mainline code and (according
> > to the users I have spoken to) frequent crashes. Union mounts is
>
> Hmm, anyone who meets crash in aufs, please let me know.
> While I never say aufs is bug-free, I don't receive such report
> recently. I always try fixing a bug as soon as possible when I got a
> report.

According Al Viro, unionfs has some fundamental architectural problems
that prevents it from being correct and leads to crashes:

http://lkml.indiana.edu/hypermail/linux/kernel/0802.0/0839.html

The main question for me is whether aufs has fixed these problems. If
it hasn't, then it can't be bug-free.

> A reply I have to write repeatedly to who have met a problem in aufs and
> reported to aufs-users ML, is "your aufs version is too old. please get
> the latest one."
> Because aufs is released every week and some linux distributions keep
> using very old aufs version, even over one year old version than thier
> release date.
>
> By the way, I don't have objection to merge Val's UnionMount into
> mainline as I have heard it is already decided.

I wish I had your confidence. :)

> > But frankly, this is an impossible problem to solve generically at the
> > file system level. When a user says, "Show the changes to the lower
> > file system in my overlaid file system," they are actually saying,
>
> Is it (mostly) possible by receiving a notification via fsnotify?
> For remote FS, their ->d_revalidate() will tell us something is changed.

Think about the case of two different RPM package database files. One
contains the info from newly installed packages on the top layer file
system. The lower layer contains info from packages newly installed
on the lower file system. You don't want either file; you want the
merged packaged database showing the info for all packages installed
on both layers. Any practical file system based system is only going
to be able to pick one file or the other, and it's going to be wrong
in some cases.

-VAL
--
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/