public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Files appear too big in `du`
Date: Thu, 12 May 2011 12:01:53 +0200	[thread overview]
Message-ID: <20110512100153.GA19381@citd.de> (raw)
In-Reply-To: <20110510153300.GA5764@citd.de>

On 10.05.2011 17:33, Matthias Schniedermeyer wrote:
> 
> > > Any idea how to debug this, or is this a known bug and waiting a few 
> > > days for 2.6.39 should fix this?
> > 
> > It doesn't appear to be doing anything wrong from your description.
> > Remember that XFS is optimised for high end storage and server
> > configurations and workloads, not typical desktop usage...
> 
> I would call it a regression.
> I reguarly follow copying/downloading with `du`, the speculative
> preallocation makes that more or less useless. Especially downloading 
> someting big from the internet which @ 231kb/s isn't exactly fast and 
> shows identical `du`s for increasingly longer periods of time.
> (Or "--apparent-size" should be made default, but that falls short with 
> sparse-files)
> 
> IMHO `du`/`ls -l` should not be able to 'see' the speculative 
> preallocation.


After digging into the log of v2.6.37..v2.6.38 i stumbled upon:

- snip -
    The allocsize mount option turns off the dynamic behaviour and fixes
    the prealloc size to whatever the mount option specifies. i.e. the
    behaviour is unchanged.
- snip -

I think Documentation/filesystems/xfs.txt is in need of an update. All 
that information in the commit-log is a little "out-of-reach" for most 
people.






Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-05-12 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 10:57 Files appear too big in `du` Matthias Schniedermeyer
2011-05-10 13:17 ` Dave Chinner
2011-05-10 15:33   ` Matthias Schniedermeyer
2011-05-12 10:01     ` Matthias Schniedermeyer [this message]
2011-05-17  8:38       ` Dave Chinner

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=20110512100153.GA19381@citd.de \
    --to=ms@citd.de \
    --cc=david@fromorbit.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