xfs
[Top] [All Lists]

Re: mount prob: "log inconsistent or not a log"

To: David Chinner <dgc@xxxxxxx>
Subject: Re: mount prob: "log inconsistent or not a log"
From: "Jonathan C. Detert" <Jonathan.Detert@xxxxxxxx>
Date: Thu, 20 Dec 2007 11:55:12 -0600
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20071220024453.GX19770@xxxxxxxx>
References: <20071220000144.GQ19770@xxxxxxxx> <4769BD13.5040303@xxxxxxx> <20071220011848.GV19770@xxxxxxxx> <20071220015425.GL4612@xxxxxxx> <20071220024453.GX19770@xxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
* Jonathan C. Detert <Jonathan.Detert@xxxxxxxx> [071219 20:44]:
> * David Chinner <dgc@xxxxxxx> [071219 19:59]:
> > On Wed, Dec 19, 2007 at 07:18:48PM -0600, Jonathan C. Detert wrote:
> > > * Timothy Shimmin <tes@xxxxxxx> [071219 18:53]:
> > > > Hi Jonathan,
> 
> -- snip --
> 
> > > > Jonathan.Detert@xxxxxxxx wrote:
> > > > >This is what /var/log/messages has to say about the mount attempt:
> > > > >-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > > > >Dec 19 17:42:30 quartz kernel: [ 9701.960000] XFS mounting filesystem 
> > > > >sdb
> > > > >Dec 19 17:42:30 quartz kernel: [ 9701.960000] XFS: Log inconsistent or 
> > > > >not 
> > > > >a log (last==0, first!=1)
> > > 
> > > --snip --
> > > 
> > > > >-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > > > >
> > > > Every 512 bytes of the log is stamped with the cycle#.
> > > > The cycle# is effectively the number of times the log has wrapped
> > > 
> > > -- snip --
> > > 
> > > > An "xfs_logprint -d /dev/sdb" will show what the cycle#s are
> > > > and where the log records are. It might give an idea of the
> > > > extent of the corruption.
> > > 
> > > Something occurred to me to point out:  the snapshot from yesterday has
> > > the same problem.  How can that be?  Is is possible that the log has
> > > been hosed for some time, and that the problem only reared its head now
> > > because I had to remount?  I.e. is it possible for an xfs fs to be
> > > mounted and used, even while the log is messed up?
> > 
> > No, it should not.

I just want to clarify - I mean to ask:

        Is it possible that an xfs filesystem which is in use by an o.s.,
        last mounted by the o.s. months ago, could have a corrupted log, and
        yet keep functioning until such time as a remount of it is attempted?

        I.e. if a log gets corrupted while the f.s. is in use, will anyone
        notice, until such time as an attempt to remount the f.s. is made?

I don't mean to ask:

        Is it possible to mount an xfs fs whose log is corrupted?

Thanks
-- 
Jon Detert
IT Systems Administrator, Milwaukee School of Engineering
1025 N. Broadway, Milwaukee, Wisconsin 53202, U.S.A.
--
Half a truth is often a great lie.


<Prev in Thread] Current Thread [Next in Thread>