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

["Jonathan C. Detert" <Jonathan.Detert@msoe.edu>]

* Timothy Shimmin <tes@sgi.com> [071219 18:53]:
> Hi Jonathan,
> 
> I'm not giving a high level view but
> in regards to the log message about the xfs log :)
> 
> Jonathan.Detert@msoe.edu 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?
-- 
Jon Detert
IT Systems Administrator, Milwaukee School of Engineering
1025 N. Broadway, Milwaukee, Wisconsin 53202, U.S.A.
--
"Most of the trouble in the world is caused by people wanting to be important."
~ T.S. Eliot