Re: [Info-ingres] Re: Mutex: ULM Pool (QEF)

Hi Vdohnal,

This could be bug 103157.

Do a trace point qs505, see if it shows any sign of LRU objects
destroyed = non-zero. If it's always zero then you may have this bug.

Martin Bowes

Hello,
we had similar problems on Solaris/Ingres 2.6 and now we have it back
again on Linux 64bit/Ingres 2006. And we have about 150 concurrent
users.

Our problem is in QSF memory. If the QSF memory is filled up more than
30%, everything goes very slowly. But unix has idle over 80%. And our
workaround is run trace point qs506 every few hours.

On Solaris two times during 2 years trace point qs506 crashed DBMS
server and our production db was inconsistent.

_______________________________________________
Info-ingres mailing list
Info-ingres@xxxxxxxxxxxxxxx
http://mailman.cariboulake.com/mailman/listinfo.py/info-ingres



.

Relevant Pages

  • Re: 2.6.19-rc2-mm1
    ... testing NMI watchdog ... ... The x86_64 nmi watchdog handling looks rather complex. ... I don't think trace all cpus ... BUG: ...
    (Linux-Kernel)
  • [BUG] 2.6.27-rc1 in ext3_find_entry
    ... in the middle of running git; I forget exactly what I was doing. ... BUG: unable to handle kernel paging request at ffff88004fc00006 ... Call Trace: ...
    (Linux-Kernel)
  • Re: cpu load balancing problem on smp
    ... this is not an irq distribution that irqbalance should give ... since this only happens when he adds more iptables rules, ... BUG: ... Call Trace: ...
    (Linux-Kernel)
  • Re: [PATCH] fix cpufreq_stats attrs removal
    ... rmmod cpufreq_stats: Ooops! ... Call Trace: ... The attached patch seems to solve both symptoms and yes... ... BUG: unable to handle kernel paging request at virtual address 6b6b6b6f ...
    (Linux-Kernel)
  • Re: NFS oops in 2.6.26rc4
    ... have a look at the actual filehandle the server is producing. ... BUG: unable to handle kernel paging request at 5a5a5a5a ... Call Trace: ...
    (Linux-Kernel)