[prev in list] [next in list] [prev in thread] [next in thread]
List: redhat-linux-cluster
Subject: Re: [Linux-cluster] GFS reports withdraw from cluster
From: Bob Peterson <rpeterso () redhat ! com>
Date: 2008-03-28 19:43:57
Message-ID: 1206733437.2741.170.camel () technetium ! msp ! redhat ! com
[Download RAW message or body]
On Fri, 2008-03-28 at 15:49 +0100, Ewald Beekman wrote:
> 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 :-(
Hi Ewald,
This likely means you have file system corruption of some kind.
There are many ways a GFS file system can get corrupted through no
fault of GFS. Please see the following entry in the FAQ:
http://sources.redhat.com/cluster/wiki/FAQ/GFS#gfs_consistency
At any rate, I recommend unmounting it from all nodes and
running gfs_fsck (from one node).
Regards,
Bob Peterson
Red Hat GFS
--
Linux-cluster mailing list
Linux-cluster@redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic