[OpenAFS] /afs area is hanging

[Simon Wilkinson]

On 7 May 2009, at 21:51, Mark Henry wrote:

>
> I ran the 'echo t' command recommended below once afs hung again.   
> It definitely put some output in dmesg.  The only D states that were  
> listed were bash sessions (I think).  It looks like they were  
> sessions that I opened after the user told me that afs was hung  
> again.  I tried to attach the dmesg output and cmdebug output but  
> the email was rejected because the log files were way too big.  Any  
> ideas of what to try next?  Or is there anything in particular that  
> I should look at in the cmdebug or dmesg output.  Thanks,

Put the files somewhere we can fetch them - either on the web, or in  
AFS. Your cmdebug output really shouldn't be that long, though (you  
want to run 'cmdebug' _not_ 'cmdebug -long)

S.