public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Isaacson <adi@hexapodia.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS stat/statvfs problems with 2.6.38-rc2-00175-g6fb1b30
Date: Wed, 2 Feb 2011 17:18:45 -0800	[thread overview]
Message-ID: <20110203011845.GL11874@hexapodia.org> (raw)
In-Reply-To: <20110202221858.GS11040@dastard>

On Thu, Feb 03, 2011 at 09:18:58AM +1100, Dave Chinner wrote:
> On Tue, Feb 01, 2011 at 06:36:44PM -0800, Andy Isaacson wrote:
> > Since updating past 2.6.37, I'm seeing du(1) sometimes report files
> > taking up 8GB even though ls(1) reports the correct size (hundreds of
> 
> It'll be the excessive specualtive preallocation bug introduced in
> .38-rc1  which is fixed in .38-rc3.

Indeed, I've been running 2.6.38-rc3-00019-gafe8a88 for 18 hours now
with the same load and not seen any issues.

Thanks,
-andy

      reply	other threads:[~2011-02-03  1:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  2:36 XFS stat/statvfs problems with 2.6.38-rc2-00175-g6fb1b30 Andy Isaacson
2011-02-02 22:18 ` Dave Chinner
2011-02-03  1:18   ` Andy Isaacson [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=20110203011845.GL11874@hexapodia.org \
    --to=adi@hexapodia.org \
    --cc=david@fromorbit.com \
    --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