[OpenAFS] advice on troubleshooting blocked cache manager on
Thu, 21 Jan 2010 14:15:58 -0500
I recall having this problem on some Solaris 9 boxes once upon a time
at a previous job. Turns out, those machines' CellServDBs had some
stale entries and -fakestat wasn't enabled. Any time you'd open
something like a "Save As" or "Open" dialog, the process would hang
for 30+ seconds while trying to stat /afs, then /afs/cell.name, then
/afs/cell.name/home, etc. all the way down to the current directory.
IIRC, limiting the cellservdb to list just cells we knew were alive
and people actually used on those machines helped... a lot.
I have no idea if this is at all related to what you are seeing (esp.
since they were different platform and running 1.2.x), but it could be
a lead you might want to investigate.
Just my two cents.
On Thu, Jan 21, 2010 at 1:36 PM, Ken Hornstein <email@example.com> wrot=
>>Hi, lately I've been encountering a lot of situations where a process
>>seems to block for a really long time trying to access something in
>>/afs; it usually succeeds, but only after several minutes. =A0This seems
>>to happen only on MacOS (1.4.11, although I saw it with 1.4.10 too).
> If it matters at all, I saw the exact same thing. =A0It seemed to be
> caused by a combination of a multihomed fileserver and AFS client
> behind a NAT (yeah, it's easy to see how that would be an issue). =A0Once
> the multihomed fileserver went away, it all fixed itself. =A0Doesn't
> really help you with the troubleshooting, but I thought it might be a
> useful datapoint.
> OpenAFS-info mailing list