Updated to 5.2, new gfs/locking messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I finally updated all my gfs cluster nodes to 5.2, when I updated the one
node that serves NFS, I started getting these in /var/log/messages:

gfs_controld[5079]: plock result write err 0 errno 2
kernel: lockd: grant for unknown block
kernel: gfs2 lock granted after lock request failed; dangling lock!
gfs_controld[5079]: plock result write err -1 errno 2
gfs_controld[5079]: plock result write err 0 errno 2

The "plock result write err" messages occur frequently. This is a centos
5.2 node serving nfs from a gfs filesystem. The nfs client that seems to
generate these errors is a fedora 9 nfs3 client, but that's just a guess.

I can't find much about these messages via google. How serious are these
messages?

Thanks,
-A
-- 
Andrew A. Neuschwander, RHCE
Linux Systems/Software Engineer
College of Forestry and Conservation
The University of Montana
http://www.ntsg.umt.edu
andrew@xxxxxxxxxxxx - 406.243.6310

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux