public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Eric Sandeen <sandeen@redhat.com>
Cc: CaT <cat@zip.com.au>, linux-ext4@vger.kernel.org
Subject: Re: 2.6.33.1: ext4 disk free weirdness
Date: Mon, 29 Mar 2010 10:53:11 -0400	[thread overview]
Message-ID: <20100329145311.GA4671@thunk.org> (raw)
In-Reply-To: <4BB0BDD2.3080100@redhat.com>

On Mon, Mar 29, 2010 at 09:48:50AM -0500, Eric Sandeen wrote:
> CaT wrote:
> > Using kernel 2.6.33.1. Am rsyncing from /data/mirror (a raid0 mount) to
> > /dev/sda1 (a usb HD). Both filesystems formatted as ext3 but mounted as
> > ext4. /mnt filesystem is only being added to and currently large files
> > (iso files 700MB-4.4GB) are being copied. When I remounted /mnt as ext3
> > I could not duplicate the issue and the amount of disk used stabilised
> > at 182G. The df results, whilst /mnt is mounted as ext4, are below:
> 
> I would say this is likely speculative allocation due to delalloc
> (ext4 has to reserve worst-case metadata amounts to prepare for
> delalloc writeback).  When the file data actually gets written out,
> the worst-case reservation is freed up again.  We also flush and
> switch to nodelalloc when the filesystem is pretty close to full.
> see ext4_nonda_switch() for example.
> 
> This looks pretty severe though, more than I would expect
> from that behavior.

This is fixed in commit d330a5bef, which which got merged post
2.6.34-rc2, and which we need to get into 2.6.33 stable.  If you
cherry-pick that commit, I think you'll see that it fixes this
problem.

						- Ted

  reply	other threads:[~2010-03-29 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29  4:57 2.6.33.1: ext4 disk free weirdness CaT
2010-03-29 14:48 ` Eric Sandeen
2010-03-29 14:53   ` tytso [this message]
2010-03-29 15:01     ` Eric Sandeen
2010-03-29 17:43       ` Justin Maggard
2010-03-29 17:51         ` Eric Sandeen
2010-03-30  1:44     ` CaT

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=20100329145311.GA4671@thunk.org \
    --to=tytso@mit.edu \
    --cc=cat@zip.com.au \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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