From: Miguel Garrido <miguel@mjgar.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: No space left, with 80 GB space free
Date: Fri, 20 May 2011 19:05:54 -0400 [thread overview]
Message-ID: <BANLkTimA_dJDNUqPUssV5ZbLTr=T7k+doA@mail.gmail.com> (raw)
In-Reply-To: <4DD6985E.8040100@wpkg.org>
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 Po=
stgreSQL, even when there is plenty of free space left?
>
>
> # df -h
> Filesystem =A0 =A0 =A0 =A0 =A0 =A0Size =A0Used Avail Use% Mounted on
> /dev/sdb4 =A0 =A0 =A0 =A0 =A0 =A0 336G =A0257G =A0 78G =A077% /mnt/bt=
rfs
>
>
> coredb=3D# DELETE FROM core_trevent where "date" < E'2011-05-07 00:00=
';
> ERROR: =A0could not write block 1014999 of relation base/16384/16521:=
No space left on device
> CONTEXT: =A0writing block 1014999 of relation base/16384/16521
>
Hi Tomasz,
What does btrfs fi df /mountpoint show?
Please see this link:
https://btrfs.wiki.kernel.org/index.php/FAQ#Help.21_Btrfs_claims_I.27m_=
out_of_space.2C_but_it_looks_like_I_should_have_lots_left.21
As well as this one:
https://btrfs.wiki.kernel.org/index.php/FAQ#Why_are_there_so_many_ways_=
to_check_the_amount_of_free_space.3F
--=20
MG
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-20 23:05 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 [this message]
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='BANLkTimA_dJDNUqPUssV5ZbLTr=T7k+doA@mail.gmail.com' \
--to=miguel@mjgar.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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;
as well as URLs for NNTP newsgroup(s).