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-46.16.0.8 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 ~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~ David Ayre Programmer/Analyst - Information Technlogy Services |
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster