From: Tomasz Chmielewski <tch@virtall.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <clm@fb.com>, Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: Re: 4.4.0 - no space left with >1.7 TB free space left
Date: Thu, 12 May 2016 15:07:42 +0900 [thread overview]
Message-ID: <69602a61b406a48ccdc6cc8d5293e639@admin.virtall.com> (raw)
In-Reply-To: <ba2a8fca73f02c328d94d541ff53a94b@admin.virtall.com>
On 2016-05-12 15:03, Tomasz Chmielewski wrote:
> FYI, I'm still getting this with 4.5.3, which probably means the fix
> was not yet included ("No space left" at snapshot time):
>
> /var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC
> LOG: could not close temporary statistics file
> "pg_stat_tmp/db_0.tmp": No space left on device
> /var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC
> LOG: could not close temporary statistics file
> "pg_stat_tmp/global.tmp": No space left on device
> /var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC
> LOG: could not close temporary statistics file
> "pg_stat_tmp/db_0.tmp": No space left on device
> /var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC
> LOG: could not close temporary statistics file
> "pg_stat_tmp/global.tmp": No space left on device
>
>
> I've tried mounting with space_cache=v2, but it didn't help.
On the good side, I see it's in 4.6-rc7.
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2016-05-12 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 9:22 4.4.0 - no space left with >1.7 TB free space left Tomasz Chmielewski
2016-02-08 11:24 ` Roman Mamedov
2016-02-08 12:15 ` Tomasz Chmielewski
2016-02-08 12:17 ` Roman Mamedov
2016-04-08 11:36 ` Tomasz Chmielewski
2016-04-08 11:53 ` Roman Mamedov
2016-04-08 13:20 ` Tomasz Chmielewski
2016-04-08 19:53 ` Duncan
2016-05-12 6:03 ` Tomasz Chmielewski
2016-05-12 6:07 ` Tomasz Chmielewski [this message]
2016-09-15 8:02 ` Roman Mamedov
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=69602a61b406a48ccdc6cc8d5293e639@admin.virtall.com \
--to=tch@virtall.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
--cc=zhaolei@cn.fujitsu.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).