Sebastian Walter wrote:
This is what /var/log/messages gives me (on nearly all nodes): Aug 18 04:39:06 compute-0-2 clurgmgrd[4225]: <err> #49: Failed getting status for RG gfs-2 and e.g. Aug 18 04:45:38 compute-0-6 clurgmgrd[9074]: <err> #50: Unable to obtain cluster lock: Connection timed out
GFS glock trimming patch *could* help. However, the lock leak *here* is from clurgmgrd (cluster infrastructure), not GFS (filesystem) itself. So these two are different issues. I vaguely recall clurgmgrd did have a bugzilla for this and was fixed sometime ago.
Lon ? -- Wendy -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
