GFS caches the information used to perform a "df" in little chunks of
cluster memory (called LVBs) associated with each bitmap lock. The data
probably got corrupted somehow. The "gfs_tool reclaim" caused the
data to be reinitialzed from disk. ("Gfs_tool shrink" should have done
that too. I'm not sure why it didn't.)
Maybe there's a bug in the lock_dlm LVB recovery code or a bug has crept
into the filesystem code.
On Thu, Nov 18, 2004 at 04:58:05PM -0600, Brynnen R Owen wrote:
> Ok, that seems to fix the reporting. Can you hit me with a
> clue-by-four as to what likely happened? We did perform a fence test
> where we ripped the power cord out from a computer. Did that hose
> metadata?
>
> On Thu, Nov 18, 2004 at 04:46:12PM -0600, Ken Preslan wrote:
> > On Thu, Nov 18, 2004 at 04:02:49PM -0600, Brynnen R Owen wrote:
> > > No change. All nodes in the cluster appear to agree on the wrong size
> > > as well.
> >
> > What does a "gfs_tool reclaim /mountpoint" do?
> >
> > --
> > Ken Preslan <kpreslan@xxxxxxxxxx>
> >
>
> --
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
> <> Brynnen Owen ( this space for rent )<>
> <> owen@xxxxxxxx ( )<>
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
--
Ken Preslan <kpreslan@xxxxxxxxxx>
