[OpenAFS] Weird client behaviour with openafs 1.4.5

[Derrick Brashear]

On Thu, Apr 17, 2008 at 5:30 AM, Berthold Cogel <cogel@uni-koeln.de> wrote:
> Hello!
>
>  Since some days I see this when I look into some AFS directories:
>
>
>  [bco@co tsm]$ ll
>  insgesamt 0
>  ?--------- ? ? ? ?             ? dsmcad.rc.linux
>  ?--------- ? ? ? ?             ? dsm.logrotate
>  ?--------- ? ? ? ?             ? dsm.opt.linux
>  ?--------- ? ? ? ?             ? dsm.opt.panfs
>  ?--------- ? ? ? ?             ? dsm.opt.vmware
>  ?--------- ? ? ? ?             ? dsm.sys.c3grid
>  ?--------- ? ? ? ?             ? dsm.sys.failure
>  ?--------- ? ? ? ?             ? dsm.sys.linux
>  ?--------- ? ? ? ?             ? dsm.sys.panfs
>  ?--------- ? ? ? ?             ? dsm.sys.vmware
>  ?--------- ? ? ? ?             ? inclexcl.linux
>  ?--------- ? ? ? ?             ? inclexcl.panfs
>  ?--------- ? ? ? ?             ? RCS
>
>  Not always the same volume but with the same server:
>
>  [bco@co tsm]$ fs checks
>  These servers unavailable due to network or server problems:
> afsfs1.rrz.uni-koeln.de.
>

Is NAT in play?
Are callbacks being lost? The 1.2.13 server almost certainly has
issues tracking the client port if NAT's in play.
The empty modes are just what Linux shows you when there's no
fetchstatus data to show.