From: Ahmed Kamal <email.ahmedkamal@googlemail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: No space left, although 16G are there
Date: Thu, 26 Nov 2009 23:41:09 +0200 [thread overview]
Message-ID: <3da3b5b40911261341x67c8b696v36f7ed2f4caefe63@mail.gmail.com> (raw)
In-Reply-To: <3da3b5b40911261338j352ee3f7i6966a3308bc6fd08@mail.gmail.com>
Hi folks,
I am running a Fedora-12 system (2.6.31.5-127.fc12.x86_64) with a
btrfs root fs. While running a "yum upgrade" with around 200MB of
updates, the system became significantly slow (3 seconds for Chrome to
scroll down after hitting space bar!) and I noticed in
/var/log/messages
Nov 26 22:12:08 localhost kernel: no space left, need 61440, 18579456
delalloc bytes, 10387451904 bytes_used, 0 bytes_reserved, 0
bytes_pinned, 0 bytes_read only, 0 may use 10406068224 total
Although "df -h" shows 16G of free space for the root fs. I thought
I'd report this. Let me know if you want more diagnostics.
Regards
next parent reply other threads:[~2009-11-26 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3da3b5b40911261338j352ee3f7i6966a3308bc6fd08@mail.gmail.com>
2009-11-26 21:41 ` Ahmed Kamal [this message]
2009-11-26 21:47 ` No space left, although 16G are there Ahmed Kamal
2009-11-26 22:46 ` Ahmed Kamal
2009-11-29 9:31 ` Moesasji
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=3da3b5b40911261341x67c8b696v36f7ed2f4caefe63@mail.gmail.com \
--to=email.ahmedkamal@googlemail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox