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: Fri, 08 Apr 2016 22:20:12 +0900 [thread overview]
Message-ID: <cb23a9f1ff0a46a4a4de284f3c8743a5@admin.virtall.com> (raw)
In-Reply-To: <20160408165332.450659c4@natsu>
On 2016-04-08 20:53, Roman Mamedov wrote:
>> > Do you snapshot the parent subvolume which holds the databases? Can you
>> > correlate that perhaps ENOSPC occurs at the time of snapshotting? If
>> > yes, then
>> > you should try the patch https://patchwork.kernel.org/patch/7967161/
>> >
>> > (Too bad this was not included into 4.4.1.)
>>
>> By the way - was it included in any later kernel? I'm running 4.4.5 on
>> that server, but still hitting the same issue.
>
> It's not in 4.4.6 either. I don't know why it doesn't get included, or
> what
> we need to do. Last time I asked, it was queued:
> http://www.spinics.net/lists/linux-btrfs/msg52478.html
> But maybe that meant 4.5 or 4.6 only? While the bug is affecting people
> on
> 4.4.x today.
Does it mean 4.5 also doesn't have it yet?
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2016-04-08 13:20 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 [this message]
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=cb23a9f1ff0a46a4a4de284f3c8743a5@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).