Known prob: MAX_LOCK_DEPTH too low?
On my x86_64 machine, I got the following message
in log (kern = 2.6.23.14)
Jan 16 04:08:38 Astara kernel: BUG: MAX_LOCK_DEPTH too low! Jan 16 04:08:38 Astara kernel: turning off the locking correctness validator.
Have no idea what caused it as I found the message on my console somewhat after the fact. The system had been up over 24 hours and is still running. System still seems 'fine' (been up 3 days now), so you can treat this as a "data point".
Quoted 11 lines · Linda Walsh
On my
x86_64machine, I got the following message
in log (kern = 2.6.23.14)Jan 16 04:08:38 Astara kernel: BUG: MAX_LOCK_DEPTH too low! Jan 16 04:08:38 Astara kernel: turning off the locking correctnessvalidator.
Have no idea what caused it as I found the message on my console somewhat after the fact. The system had been up over 24 hours and is still running. System still seems 'fine' (been up 3 days now), so you can treat this as a "data point".
Are you perhaps an XFS user?
Quoted 8 lines · Peter Zijlstra
Quoted 6 lines · Linda Walsh
On my
x86_64machine, I got the following message
in log (kern = 2.6.23.14)Jan 16 04:08:38 Astara kernel: BUG: MAX_LOCK_DEPTH too low! Jan 16 04:08:38 Astara kernel: turning off the locking correctness validator.
Quoted 9 lines
Quoted 5 lines
Have no idea what caused it as I found the message on my console somewhat after the fact. The system had been up over 24 hours and is still running. System still seems 'fine' (been up 3 days now), so you can treat this as a "data point".
Are you perhaps an XFS user?
----
Funny you should mention that... yes. However, there were no
other messages that seem to indicate that the message had anything to do with XFS. Nice shot in the dark.
Quoted 16 lines · Linda Walsh
Quoted 15 lines · Peter Zijlstra
Quoted 12 lines · Linda Walsh
On my
x86_64machine, I got the following message
in log (kern = 2.6.23.14)Jan 16 04:08:38 Astara kernel: BUG: MAX_LOCK_DEPTH too low! Jan 16 04:08:38 Astara kernel: turning off the locking correctnessvalidator.
Have no idea what caused it as I found the message on my console somewhat after the fact. The system had been up over 24 hours and is still running. System still seems 'fine' (been up 3 days now), so you can treat this as a "data point".
Quoted 7 lines
Quoted 3 lines
Are you perhaps an XFS user?
----
Funny you should mention that... yes. However, there were no
other messages that seem to indicate that the message had anything to do with XFS. Nice shot in the dark.
:-), know issue, I guess I'll up the MAX_LOCK_DEPTH for the next release. I looked at dynamically allocating that stuff, but that gets awfully painful.