All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-btrfs@vger.kernel.org, lkml@rtr.ca
Subject: Re: fallocate overhead
Date: Thu, 13 Aug 2009 10:45:23 -0400	[thread overview]
Message-ID: <20090813144523.GG4652@think> (raw)
In-Reply-To: <20090813140732.GA1915@phenom2.trippelsdorf.de>

On Thu, Aug 13, 2009 at 04:07:32PM +0200, Markus Trippelsdorf wrote:
> I was playing with the new hdparm wiper script (
> http://sourceforge.net/projects/hdparm/files/) on my Vertex SSD and
> it appears that btrfs needs a huge space overhead when dealing with
> fallocate system calls. Basically what the wiper script does is to
> fallocate one huge file using all free space minus a safety margin.
> And this margin has to be about 30% on btrfs, e.g.:

We're actively fixing this ;)  The margin is just a hard coded limit to
try and avoid enospc oopsen.  It should improve in 2.6.32.

-chris

      reply	other threads:[~2009-08-13 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 14:07 fallocate overhead Markus Trippelsdorf
2009-08-13 14:45 ` Chris Mason [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=20090813144523.GG4652@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=markus@trippelsdorf.de \
    /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.