public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Chris Pearson <kermit4@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: sb_ifree and sb_fdblocks are unequal
Date: Fri, 24 Aug 2007 08:56:26 +1000	[thread overview]
Message-ID: <20070823225626.GX72985246@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0708221713020.11516-100000@orbis.oth.net>

On Wed, Aug 22, 2007 at 05:17:33PM -0500, Chris Pearson wrote:
> I have the same problem as posted in:
> http://oss.sgi.com/archives/xfs/2006-02/msg00091.html
> 
> using xfsprogs-2.9.3  in linux  2.4.29

linux 2.4.29, eh?

I first a bunch of freespace/inode count issues quite some
time ago, but the went into a 2.6 kernel, not a 2.4 kernel.
Perhaps you should upgrade ;)

> after running xfs_repair on a read-only mounted root filesystem, xfs_check
> still shows errors:                                    
>                                                                                                                              
> # ./xfs_check.sh -f /dev/md1
> sb_ifree 993009, counted 993008
> sb_fdblocks 3119630, counted 3119633

Boot from a bootable cd (e.g. knoppix) and run repair from there
without the filesytem mounted. it should fix everything up.

> It's possible, even likely, I had corruption due to a power outtage and
> Seagate ATAPI drives that had write caching enabled by default.

Possible. no way to prove or disprove, though.

Cheers,

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

      reply	other threads:[~2007-08-23 22:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 22:17 sb_ifree and sb_fdblocks are unequal Chris Pearson
2007-08-23 22:56 ` David Chinner [this message]

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=20070823225626.GX72985246@sgi.com \
    --to=dgc@sgi.com \
    --cc=kermit4@gmail.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