[OpenAFS] Re: Directories not reachable direct after creation - linux 1.6.1

[Andrew Deason]

On Tue, 17 Jul 2012 13:51:41 +0200
Lars Schimmer <l.schimmer@cgv.tugraz.at> wrote:

> I got a more or less peristant problem on my debian linux system with
> OpenAFS 1.6.1 64bit:
> 
> 127 schimmer@tetris /afs/.cgv.tugraz.at/archive/templates %  mkdir
> TUGraz.Formulare
> 
> mkdir: kann Verzeichnis ?TUGraz.Formulare? nicht anlegen: Kein
> passendes Gerät gefunden

I assume 'No such device' is a suitable English translation for this,
yes? Does this take a while (at least a few seconds) to execute?

I also assume that the specified name did not already exist (as a dir,
or file, or mountpoint, or anything).

> Any idea?

If there were any messages in the client syslog or the server FileLog at
around the same time, that information would be helpful.

1.6.1 should contain the client behavior where we invalidate cache
information for a timed-out write op, so it's probably not just that
(although it's not perfect). If you can get this to happen while
'fstrace' tracing is on, that should say exactly what was going on at
the time. (Something like: fstrace clear cm ; fstrace setlog cmfx
-buffers 100 ; fstrace sets cm -active ; mkdir whatever & echo $! ; wait
; fstrace dump cm > /tmp/fstrace.log ; fstrace sets cm -inactive) Note
that that traces all client activity, so if you've got other
AFS-interacting stuff running on the box that you don't want to be
public information, don't upload that somewhere public.

And it doesn't really "solve" the problem, but if you see a client in
that state, you may be able to get it out with a 'fs flush .' in the
problematic directory (or 'fs flushv' to just flush everyting in the
vol). 'fs checks' and 'fs checkv' can also be tried, though it doesn't
seem like that would be the problem here.

-- 
Andrew Deason
adeason@sinenomine.net