public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Andreas Kotes <count@flatline.de>
Cc: David Chinner <dgc@sgi.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS internal error
Date: Tue, 11 Mar 2008 10:45:40 +1100	[thread overview]
Message-ID: <20080310234539.GC155407@sgi.com> (raw)
In-Reply-To: <20080310225927.GP14256@slop.flatline.de>

On Mon, Mar 10, 2008 at 11:59:27PM +0100, Andreas Kotes wrote:
> * David Chinner <dgc@sgi.com> [20080310 23:30]:
> > On Mon, Mar 10, 2008 at 01:22:16PM +0100, Andreas Kotes wrote:
> > > * David Chinner <dgc@sgi.com> [20080310 13:18]:
> > > > Yes, but those previous corruptions get left on disk as a landmine
> > > > for you to trip over some time later, even on a kernel that has the
> > > > bug fixed.
> > > > 
> > > > I suggest that you run xfs_check on the filesystem and if that
> > > > shows up errors, run xfs_repair onteh filesystem to correct them.
> > > 
> > > I seem to be having similiar problems, and xfs_repair is not helping :(
> > 
> > xfs_repair is ensuring that the problem is not being caused by on-disk
> > corruption. In this case, it does not appear to be caused by on-disk
> > corruption, so xfs_repair won't help.
> 
> ok, too bad - btw, is it a problem that I'm doing the xfs_repair on a
> mounted filesystem with xfs_repair -f -L after a remount rw?

If it was read only, and you rebooted immediately afterwards, you'd
probably be ok. Doing this to a mounted, rw filesystem is asking
for trouble. If the shutdown is occurring after you've run xfs_repair,
then it is almost certainly the cause....

I'd suggest getting a knoppix (or similar) rescue disk and repairing
from that, rebooting and seeing if the problem persists. If it
does, then we'll have to look further into it.

FWIW, you've got plenty of free inodes so this does not look
to be the same problem I've just found. 

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2008-03-10 23:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07  1:09 XFS internal error Max Waterman
2007-10-08  0:14 ` David Chinner
2007-10-08  1:54   ` Max Waterman
2007-10-08  2:32     ` Barry Naujok
2007-10-08  2:48       ` Max Waterman
2008-03-10 12:22   ` Andreas Kotes
2008-03-10 22:30     ` David Chinner
2008-03-10 22:59       ` Andreas Kotes
2008-03-10 23:45         ` David Chinner [this message]
2008-03-11 13:47           ` Andreas Kotes
  -- strict thread matches above, loose matches on Subject: below --
2006-08-26 16:06 Gerardo Exequiel Pozzi
2006-08-26 17:05 ` Jeffrey Hundstad

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=20080310234539.GC155407@sgi.com \
    --to=dgc@sgi.com \
    --cc=count@flatline.de \
    --cc=linux-kernel@vger.kernel.org \
    --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