On Mon, 18 Apr 2005, Max Matveev wrote:
"ian" == Ian Kemp ([EMAIL PROTECTED]) wrote:
ian> On Tue, 12 Apr 2005, Greg Bradner wrote:
>> Let me explain: I have one NAS1 server that has a large number of >> links to another NAS2. When I run a specific program, an in house >> tool, it stats the links; which in turn tries to mount NAS2. With the >> large number of links, the program will stat one, get 'permission >> denied', and moves to the next. On IRIX, autofs tries to mount with >> each stat.
That's exactly as designed - stat(2) follows the symlink, if you want the information about the directory or file which symlinks points to, it would have to mount first to do NFS' getattr call to get the info which stat would return. So you should expect a mount attempt for each stat.
ian> autofs on Linux shouldn't mount at all on stat unless the target is ian> contained within (not the mount point itself) the filesystem.
Why? IMO stat(2), as opposed to lstat(2), must prove the info about the node of the remote filesystem regardless of whatever it's the trigger point or a file inside the trigger point.
Equally by design.
Colour ls will mount everything when you list an autofs directory and this (the mount storm on large autofs directories) was seen as undesirable for lazy mounting in a browsable tree.
But I'm open to suggestions and ideas.
Ian
_______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
