From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Georgoulias Subject: newly added heirarchical mount points not found Date: Mon, 23 Feb 2004 19:02:31 -0600 Sender: autofs-bounces@linux.kernel.org Message-ID: <403AA2A7.3010409@motorola.com> References: <1077211015.19371.32.camel@brilong-lnx2.cisco.com> <1077211301.19371.34.camel@brilong-lnx2.cisco.com> <1077284694.21595.54.camel@brilong-lnx2.cisco.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autofs-bounces@linux.kernel.org Content-Type: text/plain; charset="us-ascii"; format="flowed" To: autofs@linux.kernel.org, raven@themaw.net Hi: I'd like to know if the heirarchical mount point behavior I've been seeing lately with autofs4 is what I should expect. When I add an additional submount point to an existing set of heirarchical mounts, I cannot access the file system referenced by the new mount point. The systems I am seeing this behavior on are Red Hat 8.0 and 7.3 systems with the 2.4.20-28.8bigmem and 2.4.20-28.7bigmem kernels (and the autofs4 module it contains) and autofs-4.1.0-2. I have a set of entries in one of my NIS automount maps very similar to these: (names changed to protect the innocent. ;) in automount map auto.stuff -- top \ /key2 bender:/vol_A/key2 \ /key3 fry:/vol_B/key3 \ /key4 fry:/vol_B/key4 -- Using "cd /stuff/top/key3" works just fine from both my linux and solaris systems. However, if I add an entry for key9: -- top \ /key2 bender:/vol_A/key2 \ /key3 fry:/vol_B/key3 \ /key9 mom:/vol_B/key9 \ /key4 fry:/vol_B/key4 -- and push out the updated map, a "cd /stuff/top/key9" only works on Solaris. The linux systems see the new entry via "ypmatch -k top auto.stuff", but I get a "No such file or directory" error when I try to cd into it. Today I tried testing this with the autofs4-2.4-module-20031201, just to see if it helped, but the problem still remains. According to the README file the new module only provides ghosting, but I figured I didn't have a lot to lose by testing it anyway. The only way I've found to safely and reliably can access the new mounts is to reboot the system, since restarting the autofs service screws up the active mounts on the apps still running and reload only checks the auto.master file for updates. Any suggestions on whether or not this is expected behavior, or if I have something set up wrong? Many thanks, Tom -- Tom Georgoulias POPI Classification [x] General Business Information [] Motorola Internal Use [] Motorola Confidential Proprietary