After sorting out the elevator with elvtune, the system is yet to
deadlock with 11 days uptime.
On 06-Dec-2000 Russell Cattelan wrote:
> Tony Gale wrote:
>> On 06-Dec-2000 Russell Cattelan wrote:
>> > Well nothing obvious jumps out at me here, other than a possible
>> > deadlock problem.
>> > Looking at the code related to the backtraces I don't see a
>> > common
>> > lock
>> > that
>> > might be tripping us up.
>> > In the backtrace; find_inode is that last function listed?
>> Well, it's first one listed, but yes.
>> > We probably need to look at the process table and find out what
>> > is
>> > running and what might be stuck.
>> I believe the two process stuck are expire (from inn) and slocate.
>> Both of these would hit the fs pretty hard.
>> I don't know the code, but could it be a resource starvation
>> such as out of inodes in the vfs?
>> > continue the system "go"
>> > break it again and do the cpu back traces.
>> Still stuck in the same places (with minor find_inode offset
> This may not be a lock contention problem then, it's possible we
> on something? waiting for some resource?
> Did you ever turn down the numbers in the elevator?
> elvtune -r 1024 <dev>
> elvtune -w 2048 <dev>
>> > Is is possible to get a serial console hooked up?
>> > I would help a great deal in capturing kdb output.
>> Ok, will do so tomorrow, and then try and force a lockup (it's
>> getting late to be at work here).
>> E-Mail: Tony Gale <gale@xxxxxxxxxxxxxxxxxx>
>> Two wrongs are only the beginning.
>> -- Kohn
>> The views expressed above are entirely those of the writer
>> and do not represent the views, policy or understanding of
>> any other person or official body.
E-Mail: Tony Gale <gale@xxxxxxxxxxxxxxxxxx>
Hmmm ... a PINHEAD, during an EARTHQUAKE, encounters an ALL-MIDGET
FIDDLE ORCHESTRA ... ha ... ha ...
The views expressed above are entirely those of the writer
and do not represent the views, policy or understanding of
any other person or official body.