On Tue, Aug 01, 2006 at 11:40:20AM +0100, Stephen Willey wrote: > We fscked the filesystem because we'd started seeing the following > errors following a power failure. > > GFS: fsid=nearlineA:gfs1.0: fatal: invalid metadata block > GFS: fsid=nearlineA:gfs1.0: bh = 2644310219 (type: exp=4, found=5) > GFS: fsid=nearlineA:gfs1.0: function = gfs_get_meta_buffer > GFS: fsid=nearlineA:gfs1.0: file = > /usr/src/redhat/BUILD/gfs-kernel-2.6.9-49/smp/src/gfs/dio.c, line = 1223 > GFS: fsid=nearlineA:gfs1.0: time = 1154425344 > GFS: fsid=nearlineA:gfs1.0: about to withdraw from the cluster > GFS: fsid=nearlineA:gfs1.0: waiting for outstanding I/O > GFS: fsid=nearlineA:gfs1.0: telling LM to withdraw > lock_dlm: withdraw abandoned memory > GFS: fsid=nearlineA:gfs1.0: withdrawn > > And another instance: > > GFS: fsid=nearlineA:gfs1.1: fatal: filesystem consistency error > GFS: fsid=nearlineA:gfs1.1: inode = 2384574146/2384574146 > GFS: fsid=nearlineA:gfs1.1: function = dir_e_del > GFS: fsid=nearlineA:gfs1.1: file = > /usr/src/redhat/BUILD/gfs-kernel-2.6.9-49/smp/src/gfs/dir.c, line = 1495 > GFS: fsid=nearlineA:gfs1.1: time = 1154393717 > GFS: fsid=nearlineA:gfs1.1: about to withdraw from the cluster > GFS: fsid=nearlineA:gfs1.1: waiting for outstanding I/O > GFS: fsid=nearlineA:gfs1.1: telling LM to withdraw > lock_dlm: withdraw abandoned memory > GFS: fsid=nearlineA:gfs1.1: withdrawn What kind of fencing are you using in the cluster? Trying to understand how this might have happened. Dave -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
