On Mon, 2012-09-24 at 17:14 -0300, Leonardo Chiquitto wrote: > Hi, > > If you try to access an automounted directory and the mount operation fails, > the attributes of the directory (owner, group, mode, access time) are lost. > This happens only when AutoFS' browse mode (ghosting) is enabled. > > How to reproduce the problem: > > Make sure you have BROWSE_MODE="yes" in /etc/sysconfig/autofs. > > 1. Add a simple indirect mount map (it's required that the server does NOT > export the /notexported directory): > > # cat /etc/auto.master > /nfs /etc/auto.nfs > > # cat /etc/auto.nfs > v2 server:/notexported > > 2. Restart AutoFS and try to access the directory: > > # cd /nfs/v2 > -bash: cd: /nfs/v2: No such file or directory > > # ls -la /nfs > ls: cannot access /nfs/v2: No such file or directory > total 4 > drwxr-xr-x 3 root root 0 Sep 24 21:43 . > drwxr-xr-x 28 root root 4096 Sep 24 21:25 .. > d????????? ? ? ? ? ? v2 > > This problem is reproducible on recent upstream kernels such as 3.6.0-rc6. > I found out that the last kernel version that does not exhibit the bug is > 2.6.37. Between 2.6.37 and 2.6.38 there were quite some changes in > AutoFS/VFS and my attempts to bisect the problem were frustrated by > early crashes. > > Any ideas? Not really. It would be best to start with an full autofs debug log so we can see what is happening within automount and work back from there. We'll probably need to look at the dentry itself as well to see if we can get any info about where it came from possibly, with a kernel dump. Ian -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
