Re: unacceptable bug in autofs kernel module

[ramana <ramana@intraperson.com>]

Ian Kent wrote:

>On Thu, 3 Feb 2005 mmarion@qualcomm.com wrote:
>
>  
>
>>On 28 Dec, ramana wrote:
>>
>>    
>>
>>>Here is the bug in autofs3 module which causing so much pain. It simply 
>>>stopped me from adding much more interesting features to Autodir 
>>>http://www.intraperson.com/autodir/
>>>      
>>>
>>[snip]
>>    
>>
>>>Because of this, user space test program reporting like this:
>>>
>>>fail : /test/t944 : No such file or directory
>>>fail : /test/t4187 : No such file or directory
>>>      
>>>
>>Hmm.. I wonder if this might be related to a weirdness we're seeing. Running
>>autofs-4.1.3 with previous latest patch to kernel (pre-2005 release) and users
>>use LSF to submit batch jobs to hosts.  On linux hosts, user level programs
>>will sometimes exit quickly with a "file does not exist" error, even though you
>>can login to the host and see the file/dir just fine.  As a hacked
>>work-around, we have a pre-exec script that tries to stat all the directories
>>they need to force the mounts to happen before their program touches the
>>files.
>>    
>>
>
>Does the stat actually mount anything?
>It shouldn't?
>
>Ian
>
>
>  
>
I moved latest version Autodir to autofs 4 kernel module and so far all 
stress tests tell me autofs4 protocol is performing well without these 
ENOENT errors. I have to do little bit more tests before concluding 
anything as final.

For more details check http://www.intraperson.com/autodir/.
DVersion: Autodir 0.93.0 and above.

Regards
ramana

-- 
http://www.intraperson.com