Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756860AbXKKW31 (ORCPT ); Sun, 11 Nov 2007 17:29:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755454AbXKKW3S (ORCPT ); Sun, 11 Nov 2007 17:29:18 -0500 Received: from sovereign.computergmbh.de ([85.214.69.204]:57114 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755151AbXKKW3S (ORCPT ); Sun, 11 Nov 2007 17:29:18 -0500 Date: Sun, 11 Nov 2007 23:29:16 +0100 (CET) From: Jan Engelhardt To: Roland Kuhn cc: Linux Kernel Mailing List , Frans Pop Subject: Re: Bind mount bug? In-Reply-To: <200711111106.53494.elendil@planet.nl> Message-ID: References: <200711111106.53494.elendil@planet.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 866 Lines: 25 >> I'm not sure whether this is a bug or expected behavior. >> Suppose I create a "looped" bind mount situation as follows. >> >> # mkdir test >> # touch test/foo >> # mkdir bindtest >> # touch bindtest/bar >> # mkdir bindtest/test >> # mount --bind test/ bindtest/test/ >> # ls bindtest/test/ >> foo >> # mount --bind bindtest/ test/ > >This mounts the bindtest/ tree on test/ _without_ copying the mount >points which are found on subtrees. This is necessary to avoid loops >in the filesystem (bind mounts are somewhat like hardlinks on >directories, just without the headaches). What you seek is mount --rbind. - 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/