From: Roman Mamedov <rm@romanrm.net>
To: fdmanana@gmail.com
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel 4.4.0 intermittent ENOSPC during heavy data write and concurrent snapshotting
Date: Thu, 21 Jan 2016 14:02:09 +0500 [thread overview]
Message-ID: <20160121140209.28d0072e@natsu> (raw)
In-Reply-To: <CAL3q7H6y3-8PhZOiBVxszZV5DN-c81EsQ_NjMaHmgGmJrc9aQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
Hello,
On Wed, 20 Jan 2016 20:46:39 +0000
Filipe Manana <fdmanana@gmail.com> wrote:
> Try this: https://patchwork.kernel.org/patch/7967161/
>
> (It's not a regression in 4.4 however, it has been there for a long time)
I can't reproduce the problem on 4.3.3 or 3.18.22. On 4.4.0 it occurs almost
instantly (faster if not including 'sync' into the dd cycle).
The patch seems to fix it for 4.4.0, thanks.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-01-21 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 15:29 Kernel 4.4.0 intermittent ENOSPC during heavy data write and concurrent snapshotting Roman Mamedov
2016-01-20 20:46 ` Filipe Manana
2016-01-21 9:02 ` Roman Mamedov [this message]
2016-01-22 12:07 ` Austin S. Hemmelgarn
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=20160121140209.28d0072e@natsu \
--to=rm@romanrm.net \
--cc=fdmanana@gmail.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;
as well as URLs for NNTP newsgroup(s).