[Lustre-discuss] Looping in __d_lookup

[Robin Humble]

On Wed, May 21, 2008 at 08:04:27PM -0600, Andreas Dilger wrote:
>On May 21, 2008  21:05 +0200, Jakob Goldbach wrote:
>> I'm running 1.6.4.3 patchless as well against an 2.6.18 vanilla kernel.
>> Or at least that is what I thought. OpenVz patch effectively makes the
>> kernel a 2.6.18++ kernel because they add features from newer kernels in
>> their maintained 2.6.18 based kernel.  
>> 
>> So the lockup in __d_lookup may just relate to newer patchless clients. 
>> 
>> I got a debug patch from the OpenVz community which indicate dcache
>> chain corruption in a lustre code path. 
>
>Do you have the fixes for the statahead patches, disable statahead via
>"echo 0 > /proc/fs/lustre/llite/*/statahead_max", or can you try out the
>v1_6_5_RC4 tag from CVS (which also contains those patches)?

all of our __d_lookup soft lockups have been when running with 0 in
/proc/fs/lustre/llite/*/statahead_max

I'll try v1_6_5_RC4 now - should be fun :-)

cheers,
robin