All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: No space left, with 80 GB space free
Date: Mon, 16 May 2011 20:08:23 +0200	[thread overview]
Message-ID: <4DD16817.9020302@wpkg.org> (raw)

I've been trying to run PostgreSQL with a ~20-30 GB database on a btrfs 
filesystem (rest of the filesystem filled with KVM images, compressed 
archives etc.). Snapshots are cool, and let you rollback to a different 
database version easily ;)

Unfortunately, running PostgreSQL on btrfs wasn't very reliable as I was 
getting rather frequent "No space left" for some disk intensive 
operations (CREATE INDEX, REINDEX, VACUUM ANALYZE).

As the error happens, I still have around 80 GB free space on the 
filesystem:

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb4             336G  255G   80G  77% /mnt/btrfs


What's even more interesting, after the error happened, I'm able to 
write a ~85 GB file with dd before it exits with "out of space" (with 
and without the oflag=direct):

# dd if=/dev/urandom of=bigfile bs=1M
dd: writing `bigfile': No space left on device
81056+0 records in
81055+0 records out
84992327680 bytes (85 GB) copied, 9429.28 s, 9.0 MB/s


The kernel used was 2.6.39-rc5.

If it matters, I had the filesystem mounted with compress-force flag:

/dev/sdb4 on /mnt/btrfs type btrfs (rw,noatime,compress-force)



-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2011-05-16 18:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 18:08 Tomasz Chmielewski [this message]
2011-05-20 16:35 ` No space left, with 80 GB space free Tomasz Chmielewski
2011-05-20 23:05   ` Miguel Garrido
2011-05-20 23:49     ` Tomasz Chmielewski
2011-06-18 18:52     ` Tomasz Chmielewski
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=4DD16817.9020302@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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.