linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Miguel Garrido <miguel@mjgar.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: No space left, with 80 GB space free
Date: Sat, 18 Jun 2011 20:52:25 +0200	[thread overview]
Message-ID: <4DFCF3E9.1080508@wpkg.org> (raw)
In-Reply-To: <BANLkTimA_dJDNUqPUssV5ZbLTr=T7k+doA@mail.gmail.com>

On 21.05.2011 01:05, Miguel Garrido wrote:
> On Fri, May 20, 2011 at 12:35 PM, Tomasz Chmielewski<mangoo@wpkg.org>  wrote:
>>
>> Nobody has a clue what makes btrfs run out of space when used with PostgreSQL, even when there is plenty of free space left?
>>
>>
>> # df -h
>> Filesystem            Size  Used Avail Use% Mounted on
>> /dev/sdb4             336G  257G   78G  77% /mnt/btrfs
>>
>>
>> coredb=# DELETE FROM core_trevent where "date"<  E'2011-05-07 00:00';
>> ERROR:  could not write block 1014999 of relation base/16384/16521: No space left on device
>> CONTEXT:  writing block 1014999 of relation base/16384/16521

Hmm, this "No space left on device" only shows up if I write to the 
btrfs filesystem relatively fast.

For example, this way, I can only write around 1 GB (~60 MB/s write):

# cp -v acer.img.xz /mnt/btrfs/
`ac.img.xz' -> `/mnt/btrfs/ac.img.xz'
cp: writing `/mnt/btrfs/ac.img.xz': No space left on device


This way, when the writes are CPU-bound, I'm able to fully fill the 
btrfs filesystem (~8 MB/s):

# dd if=/dev/urandom of=/mnt/btrfs/bigfile


Delayed allocation?

-- 
Tomasz Chmielewski
http://wpkg.org

  parent reply	other threads:[~2011-06-18 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 18:08 No space left, with 80 GB space free Tomasz Chmielewski
2011-05-20 16:35 ` Tomasz Chmielewski
2011-05-20 23:05   ` Miguel Garrido
2011-05-20 23:49     ` Tomasz Chmielewski
2011-06-18 18:52     ` Tomasz Chmielewski [this message]
2011-08-10 10:38     ` Tomasz Chmielewski

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=4DFCF3E9.1080508@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miguel@mjgar.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;
as well as URLs for NNTP newsgroup(s).