Re: [PATCH 05/24] Unionfs: Copyup Functionality

[Shaya Potter <spotter@cs.columbia.edu>]

On Mon, 2007-01-08 at 13:29 -0800, Andrew Morton wrote:
> On Sun,  7 Jan 2007 23:12:57 -0500
> "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu> wrote:
> 
> > From: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
> > 
> > This patch contains the functions used to perform copyup operations in unionfs.
> 
> What is a copyup operation and why does it exist?
> 
> It seems to be copying the entire contents of certain files.  That's not a
> thing I'd have expected to see in a union filesystem.  Explain it all,
> please?  (Somewhere where the info will be retained for posterity - a
> random email is good, but not sufficient...)

to do the random e-mail, it's because it just doesn't union
"directories", but lets you assign read-write, read-only properties to
them.

If you try to modify a file on a read-only layer, it will be copied to
the top most layer (has to be read-write) and then modified.  It can be
slow though (imagine modifying a 1GB file).

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/