GFS consistency error

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

 



Hi,

One node in our two-node cluster goes down twice a day now (after this
message it's fenced by the other node) with the following messages:

Nov  9 11:13:12 node1 kernel: GFS: fsid=my_cluster:vol3.1: fatal: filesystem consistency error
Nov  9 11:13:12 node1 kernel: GFS: fsid=my_cluster:vol3.1:   inode = 609689846/609689846
Nov  9 11:13:12 node1 kernel: GFS: fsid=my_cluster:vol3.1:   function = gfs_change_nlink
Nov  9 11:13:12 node1 kernel: GFS: fsid=my_cluster:vol3.1:   file = /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/inode.c, line = 844
Nov  9 11:13:12 node1 kernel: GFS: fsid=my_cluster:vol3.1:   time = 1194603192
Nov  9 11:13:12 node1 kernel: GFS: fsid=my_cluster:vol3.1: about to withdraw from the cluster
Nov  9 11:13:12 node1 kernel: GFS: fsid=my_cluster:vol3.1: telling LM to withdraw

This is on a RHEL5-clone.

Is this really a GFS fs error and should we do a fsck?  If yes, question is
of course how this inconsistency could happen.  If not, what can we do?

Thanks,

--
--    Jos Vos <jos@xxxxxx>
--    X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--    Amsterdam, The Netherlands        |     Fax: +31 20 6948204

--
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