All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: xfs@oss.sgi.com
Subject: Files appear too big in `du`
Date: Tue, 10 May 2011 12:57:00 +0200	[thread overview]
Message-ID: <20110510105700.GA20307@citd.de> (raw)

Hi


Since a few weeks i'm experiencing an annoying 'thing' where files are 
often too big in `du` and directory totals are to high in `ls -l`.

I appears that files, which are in the process of beeing 
copied/downloaded/whatever, grow in large chunks ahead of time, while 
the actual file-content is beeing copied into the files. And then it 
appears that the last chunk isn't shrunk after the process is finished.
Neither xfs_bmap (Version 3.1.5) nor filefrag show anything beyond the 
extent that compromises the actual file-content.

I've noticed this at least with:
- "git gc"
- cp -a
- rsync
- downloads with firefox (technically Iceweasel)

Kernel is currently 2.6.38.5, Distribution is an up-to-date Debian-SID.
mount is with default-parameters, except "noatime".

Any idea how to debug this, or is this a known bug and waiting a few 
days for 2.6.39 should fix this?




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-10 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 10:57 Matthias Schniedermeyer [this message]
2011-05-10 13:17 ` Files appear too big in `du` Dave Chinner
2011-05-10 15:33   ` Matthias Schniedermeyer
2011-05-12 10:01     ` Matthias Schniedermeyer
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=20110510105700.GA20307@citd.de \
    --to=ms@citd.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.