shared libs in AFS

[Dave Morrison]

Hi all,

I'm running a arla-0.22, linux 2.2.1 on a dual-CPU box.  We have an application
that references a lot of shared libraries that are stored in an AFS volume. 
When arla is first started on the machine, all is well, and we can see and load
the libraries.  After a time (few hours or so), an odd thing happens - I can
still ls each of the shared libraries, I can cat each of them to /dev/null, and
I can cp each out of AFS.  If I retrieve one of the libraries from AFS by way of
a different machine running Transarc's AFS and compare it to one retrieved using
arla they seem to be byte for byte identical.  However, running ldd on our main
application reports that some of the shared libraries can't be found.  We are
successfully using other shared libraries from the same directory and the
application had been successfully using the libraries in question up to the
point that they became unloadable.  Once in this state, it seems to be
persistent.  I really need to stop and restart arla for it to clear.  I would be
perfectly willing to believe this is a linux question and not an arla one,
except that we don't see this behavior on machines running Transarc's AFS (OK,
and those other machines are also not running 2.2.1!) 

If anyone has tips on how I could diagnose the problem, how I could collect good
debug info or something, I'd be very grateful.

Thanks,
Dave

-- 
David Morrison  Brookhaven National Laboratory  phone: 516-344-5840
                Physics Department, Bldg 510 C    fax: 516-344-3253
		          Upton, NY 11973-5000  email: dave at bnl.gov