We have a RHEL4 2 node cluster running on HP Integrity servers (rx4640, 4 Itanium's, 32GB RAM each). The GFS is running on top of a SAN (EMC Cx380's). We get these kinds of errors: Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: fatal: invalid metadata block Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: bh = 16659526 (type: exp=5, found=4) Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: function = gfs_get_meta_buffer Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: file = /builddir/build/BUILD/gfs-kernel-2.6.9-75/up/src/gfs/dio.c, line = 1223 Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: time = 1206652995 Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: about to withdraw from the cluster Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: waiting for outstanding I/O Mar 27 22:23:15 idefix kernel: GFS: fsid=alpha_cluster:orabck.0: telling LM to withdraw Mar 27 22:23:15 idefix kernel: lock_dlm: withdraw abandoned memory and then the filesystem is gone :-( We are up2date with current patch levels: GFS-6.1.15-1 GFS-kernel-2.6.9-75.12 cman-kernel-2.6.9-53.9 cman-1.0.17-0.el4_6.5 Not sure whether this is a SAN issue (that would be bad, 'cause a lot of systemen are dependant of the SAN) or OS or inside the GFS? Any help is greatly appreciated. Ewald... -- Ewald Beekman, Security Engineer, Academic Medical Center, dept. ADICT/AD Server en Netwerkbeheer, The Netherlands ## Your mind-mint is: Blessed is the man who, having nothing to say, abstains from giving wordy evidence of the fact. -- George Eliot -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
