Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Aug 2002 17:31:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Aug 2002 17:31:32 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:64772 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 20 Aug 2002 17:31:30 -0400 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: automount doesn't "follow" bind mounts Date: 20 Aug 2002 14:35:26 -0700 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2002 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2328 Lines: 57 Followup to: By author: "H. Peter Anvin" In newsgroup: linux.dev.kernel > > Followup to: > By author: Matt Bernstein > In newsgroup: linux.dev.kernel > > > > I tried to subscribe to the autofs list, but majordomo isn't replying to > > me! I think this is a problem in the automount daemon rather than the > > kernel autofs code itself. > > > > I'm trying to automount our home dirs as > > /homes/$USERNAME > > which should bind mount to > > :/home/$SERVER/$HOMENAME/$USERNAME > > which should bind mount to > > :/home/$SERVER/$VOLUME/$PATH/$USERNAME > > which (phew!) will be an NFS mount to > > $SERVER:/$VOLUME/$PATH/$USERNAME > > > > The idea is that: > > (1) `/bin/pwd` = "/homes/$USERNAME" > > (2) when you run "quota" it'll only report for $SERVER:/$VOLUME > > > > Now.. this all works perfectly if before looking at /homes/$USERNAME you > > look at firstly /home/$SERVER/$VOLUME/$PATH/$USERNAME and then secondly > > /home/$SERVER/$HOMENAME/$USERNAME, because the bind mounts have something > > to bind to. Of course you shouldn't need to know the middle bits, but you > > could look them up. Currently the binds mount fail and automount drops in > > symlinks; this satisfies (2) above, but unfortunately not (1). > > > > I hope someone can make sense of this. Is it different in autofs4? > > > > This is unfortunately nearly impossible to solve. It's a known bug, > but it's questionable if anything can be done about it. > > For right now, autofs cannot bind-mount to a mount from the same > automount point (the problem is with the double-use of /home/$SERVER > in your case.) > Actually, if you're using autofs v3, which it sounds like you're doing, it's even more broken, since autofs v3 doesn't support multilevel mounts. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/