public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan C. Detert" <Jonathan.Detert@msoe.edu>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: mount prob: "log inconsistent or not a log"
Date: Thu, 20 Dec 2007 11:55:12 -0600	[thread overview]
Message-ID: <20071220175512.GA6023@msoe.edu> (raw)
In-Reply-To: <20071220024453.GX19770@msoe.edu>

* Jonathan C. Detert <Jonathan.Detert@msoe.edu> [071219 20:44]:
> * David Chinner <dgc@sgi.com> [071219 19:59]:
> > On Wed, Dec 19, 2007 at 07:18:48PM -0600, Jonathan C. Detert wrote:
> > > * Timothy Shimmin <tes@sgi.com> [071219 18:53]:
> > > > Hi Jonathan,
> 
> -- snip --
> 
> > > > 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?
> > 
> > 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.

  reply	other threads:[~2007-12-20 17:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20  0:01 mount prob: "log inconsistent or not a log" Jonathan.Detert
2007-12-20  0:53 ` Timothy Shimmin
2007-12-20  1:16   ` Jonathan C. Detert
2007-12-20  4:44     ` Timothy Shimmin
2007-12-20  5:04       ` Jonathan C. Detert
2007-12-20  5:45         ` Timothy Shimmin
2007-12-20 19:54         ` Jonathan C. Detert
2007-12-20  1:18   ` Jonathan C. Detert
2007-12-20  1:54     ` David Chinner
2007-12-20  2:44       ` Jonathan C. Detert
2007-12-20 17:55         ` Jonathan C. Detert [this message]
2007-12-21  0:47           ` Timothy Shimmin
2007-12-21  1:55             ` Jonathan C. Detert
2007-12-21  6:40               ` Timothy Shimmin
2007-12-21 23:19                 ` Jonathan C. Detert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071220175512.GA6023@msoe.edu \
    --to=jonathan.detert@msoe.edu \
    --cc=dgc@sgi.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox