Date: Wed, 16 Jan 2008 12:13:27 -0500
Message-Id: <200801161713.m0GHDRUN023917@agora.fsl.cs.sunysb.edu>
From: Erez Zadok <ezk@cs.sunysb.edu>
To: Paul Albrecht <albrecht@rdi1.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unionfs, cow, and whiteout 
In-reply-to: Your message of "Wed, 16 Jan 2008 10:27:13 CST."
             <1200500833.11000.0.camel@thinix-laptop> 
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1523
Lines: 42

In message <1200500833.11000.0.camel@thinix-laptop>, Paul Albrecht writes:
> Hi,
> 
> I have a question about how unionfs handles file deletion when a write
> enabled file system is union mounted over a read only file system. For
> example, I do something like the following:
> 
> mount -t unionfs -o dirs=/cow=rw:/rofs=ro unionfs /mnt
> 
> If I create and delete a file in /mnt which is not present in /rofs it
> persists as whiteout in the cow file system which is not what I would
> have expected.

Paul, the alternative is to scan all branches (there could be many) to
ensure that the file may not exist by that name anywhere else, and if so,
try to delete all instances of it.  This was deemed too expensive and
complex.

Another possible problem is that if you choose to insert a new branch in the
middle, and you didn't have the whiteout, you may re-expose the file name
unintentionally.

You might want to take a look at our unionfs-odf version: it places
whiteouts in a separate persistent store outside the branches, not as .wh.*
files in individual branches.

> Why does the deleted file persist as whiteout in the /cow file system of
> the union mount?
> 
> Please cc me in your response as I'm not subscribed to the lkml.
> 
> -- 
> 
> Paul Albrecht

Cheers,
Erez.
--
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/