linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <tch@virtall.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 4.4.0 - no space left with >1.7 TB free space left
Date: Mon, 08 Feb 2016 21:15:38 +0900	[thread overview]
Message-ID: <5752ed994dd80b90cf91f7006f037a05@admin.virtall.com> (raw)
In-Reply-To: <20160208162410.58cb2b4a@natsu>

On 2016-02-08 20:24, Roman Mamedov wrote:
> On Mon, 08 Feb 2016 18:22:34 +0900
> Tomasz Chmielewski <tch@virtall.com> wrote:
> 
>> Linux 4.4.0 - btrfs is mainly used to host lots of test containers,
>> often snapshots, and at times, there is heavy IO in many of them for
>> extended periods of time. btrfs is on HDDs.
>> 
>> 
>> Every few days I'm getting "no space left" in a container running 
>> mongo
>> 3.2.1 database. Interestingly, haven't seen this issue in containers
>> with MySQL. All databases have chattr +C set on their directories.
> 
> Hello,
> 
> Do you snapshot the parent subvolume which holds the databases? Can you
> correlate that perhaps ENOSPC occurs at the time of snapshotting?

Not sure.

With the last error, a snapshot was made at around 06:06, while "no 
space left" was reported on 06:14. Suspiciously close to each other, but 
still, a few minutes away.

Unfortunately I don't have error log for previous cases.


> If yes, then
> you should try the patch https://patchwork.kernel.org/patch/7967161/
> 
> (Too bad this was not included into 4.4.1.)

I'll keep an eye on it, thanks.


Tomasz Chmielewski
http://www.ptraveler.com


  reply	other threads:[~2016-02-08 12:15 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 [this message]
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
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=5752ed994dd80b90cf91f7006f037a05@admin.virtall.com \
    --to=tch@virtall.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.net \
    /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).