|What do you mean by pounded exactly ?|
We have an ongoing issue, similar... when we have about a dozen users using both smb/nfs, and at some seemingly random point in time our dlm_senddd chews up 100% of the CPU... then dies down at on its own after quite a while. Killing SMB processes, shutting down SMB didn't seem to have any affect... only a reboot cures it. I've seen this described (if this is the same issue) as a "soft lockup" as it does seem to come back to life:
We've been assuming its a kernel/dlm version as we are running 2.6.9-55.0.6.ELsmp with dlm-kernel 2.6.9-220.127.116.11
we were going to try a kernel update this week... but you seem to be using a later version and still have this problem ?
Could you elaborate on "getting pounded by dlm" ? I've posted about this on this list in the past but received no assistance.
On 1-Apr-08, at 5:19 PM, Andrew A. Neuschwander wrote:
I have a GFS cluster with one node serving files via smb and nfs. Under
fairly light usage (5-10 users) the cpu is getting pounded by dlm. I am
using CentOS5.1 with the included kernel (2.6.18-53.1.14.el5). This sounds
like the dlm issue mentioned back in March of last year
that was resolved in 2.6.21.
Has (or will) this fix be back ported to the current el5 kernel? Will it
be in RHEL5.2? What is the easiest way for me to get this fix?
Also, if I try a newer kernel on this node, will there be any harm in the
other nodes using their current kernel?
Andrew A. Neuschwander, RHCE
Linux Systems Administrator
Numerical Terradynamic Simulation Group
College of Forestry and Conservation
The University of Montana
andrew ntsg umt edu - 406.243.6310
Linux-cluster mailing list
Linux-cluster redhat com
Programmer/Analyst - Information Technlogy Services
Emily Carr Institute of Art and Design
Vancouver, B.C. Canada