[Bug 491977] [NEW] am-utils reads but ignores cache_duration settings in amd.conf

[James Sparenberg]

Public bug reported:

Binary package hint: am-utils

Settings on our systems has cache_duration =  1800  (30 minutes) what we
are seeing however is that the mount disappears with 2 minutes (amd
default timeout) of last access.  This is occurring most noticeably now
that we are switching to karmic 64bit and new servers.

Impact is severe as time outs on directories are happening during the
build process, as it can sometimes be 3 or 4 minutes before the dir or
it's associated libs are needed again. (cross compile environment micro
OS)

The only way we have found to hold a dir open is to have a user cd into
a dir.  This is why our home dirs don't disappear.

an ls of a dir will bring the mount back but a call to a specific file
will fail.  so if I do

ls /auto/mount/

I get a return of the correct files in that dir, but if I do

/auto/mount/somelib.so.1

I will get a file not found error.  Yes it seems that if we modify the
make file to do an ls prior to every section of all potential dirs it
might work around, however this is not viable.  Make files are too long
each and too complex in the manor in which they call each other.  (Add
in parallel building and it's way to much to work around.).

Under 9.04 this action was not observed.  Under 9.10 both 32 and 64 bit
however we see the following when full logging is turned on.

Here is the log snip snip when the dir is mounted by doing an ls

*****
    Dec  2 17:52:34 guitar amd[20263]/info:  netapp1:/vol/vol1/linux-bin
    mounted fstype nfs on /.amd/netapp1/vol/vol1/linux-bin 
    Dec  2 17:52:34 guitar amd[20263]/info:  /volume/linux-bin set to
    timeout in 1800 seconds
*****

Notice that it did read and acknowledge reading the 1800 second param
our amd.conf sets.  Then you see this.

*****
    Dec  2 17:54:35 guitar amd[20263]/info:  call_mountd: NFS version 3,
    mount version 3
    Dec  2 17:54:35 guitar amd[20263]/info:  removing mountpoint directory
    '/.amd/netapp1/vol/vol1/linux-bin'
*****

You'll notice from the time stamps that it's only 2 minutes after
mounting that it auto unmounted the dir.  Instead of the 1800 sec set in
the param.  2 minutes according to the man page is the default timeout.
One of our QA people said that they suspected a variable mismatch is the
culprit.  However they looked at me with a blank stare when I asked if
they could help me in tracing it out. ;)

Please contact me directly if you need to.  I'd like to help how I can
in getting this one right.

** Affects: am-utils (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd auto-mount mount nfs

-- 
am-utils reads but ignores cache_duration settings in amd.conf
https://bugs.launchpad.net/bugs/491977
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs