From: Frans Pop <elendil@planet.nl>
To: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Subject: Re: Bind mount bug?
Date: Sun, 11 Nov 2007 23:40:44 +0100
User-Agent: KMail/1.9.7
Cc: linux-kernel@vger.kernel.org
References: <200711111106.53494.elendil@planet.nl> <09A755B9-27C1-4B54-834C-FDA9EE806042@e18.physik.tu-muenchen.de>
In-Reply-To: <09A755B9-27C1-4B54-834C-FDA9EE806042@e18.physik.tu-muenchen.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200711112340.45400.elendil@planet.nl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1042
Lines: 37

On Sunday 11 November 2007, Roland Kuhn wrote:
> This mounts the bindtest/ tree on test/ _without_ copying the mount
> points which are found on subtrees.

Right. I guess this is the key point that tripped me up.

> So, you see, test/test/test/a was (as it should) physically created  
> in test/test, where it is shadowed by the bind mount as long as that  
> is not removed.

Which means that to continue the example from my follw-up mail:

> # ls bindtest/test
> foo
> # umount test
> # ls test
> foo
# umount bindtest/test
# ls bindtest/test
baz

And there indeed is the missing file.

> Nothing vanishes into "thin air" ;-)

Yeah, I saw that syntax error after sending the mail "into space" would have 
been OK too, but not my combining the two :-)

Thanks for the explanation!

Cheers,
FJP
-
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/