From: Ingo Koehne Subject: Re: unable to umount after chroot to a NFS mounted partition Date: Mon, 6 May 2002 08:18:24 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20020506061824.GA18214@noo.localnet> References: <20020505170924.GA837@noo.localnet> <15573.35005.147582.796024@charged.uio.no> <20020505203431.GA893@noo.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linux FSdevel Return-path: To: Trond Myklebust Content-Disposition: inline In-Reply-To: <20020505203431.GA893@noo.localnet> List-Id: linux-fsdevel.vger.kernel.org On Sun, May 05, 2002 at 10:34:31PM +0200, Ingo Koehne wrote: > i just found out that the problem only arises when mounting the root > filesystem of the requested nfs server. I checked that it doesnt matter wether the root directory of that partition was mounted or an arbitrary subdirectory on the same fs (containing the necessary files to chroot into it). It also doesnt matter if the mount was read-only or not. > I was not aware that this could be a problem as i assumed that the > problem has to be on the client side. It also doesnt matter if the server is in kernel or userspace. The problem has to be on the client side, but HOW can the client even know if the filesystem is mounted at root on the server site. And how can that in turn create weired interactions with chroot? I am quite lost here, am i missing something? > When trying to unmount the partition the server (host: noo) confirmeed > the unmount request: ... > but the client side (host: mu) failed to unmount. The server assumes the unmount was successful, the client is not listed with any mounts. However, accessing files from the client is still possible (seems strange to me, 'mnt' and 'umnt' obviously have other meaning than i expected). ingo