public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Albrecht <albrecht@rdi1.com>
To: linux-kernel@vger.kernel.org
Subject: unionfs, cow, and whiteout
Date: Wed, 16 Jan 2008 10:27:13 -0600	[thread overview]
Message-ID: <1200500833.11000.0.camel@thinix-laptop> (raw)

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.

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

             reply	other threads:[~2008-01-16 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 16:27 Paul Albrecht [this message]
2008-01-16 17:13 ` unionfs, cow, and whiteout Erez Zadok
2008-01-16 19:48   ` Paul Albrecht
2008-01-16 20:18     ` Erez Zadok

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=1200500833.11000.0.camel@thinix-laptop \
    --to=albrecht@rdi1.com \
    --cc=linux-kernel@vger.kernel.org \
    /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