[OpenAFS-devel] Odd Behavior with 1.4.2fc3

chas williams - CONTRACTOR chas@cmf.nrl.navy.mil
Thu, 14 Sep 2006 11:03:49 -0400


In message <45096BC6.7000608@cert.org>,Jason McCormick writes:
>Jeffrey Altman wrote:
>> chas williams - CONTRACTOR wrote:
>>> In message <4506ED3C.6090302@secure-endpoints.com>,Jeffrey Altman writes:
>>>> 0x66 is VNOVNODE.
>>> from the fileserver/volserver then?
>> 
>> Yes.
>
>Is there a good way to debug this problem?

i cant think of a good reason for the server to reply with VNOVNODE unless
the local cache has become corrupted.  this would explain why the fs flush
would clear up the problem (atleast for my case).

when you get a broken file, turn on fstrace and make an access to
that file.  stop fstrace, fstrace dump the output and then get a 
copy of the cache manager contents with 'cmdebug localhost 7001 -long'
'fs examine' on the file would be useful as well.