From: Filipe Manana <fdmanana@gmail.com>
To: Roman Mamedov <rm@romanrm.net>
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: Wed, 20 Jan 2016 20:46:39 +0000 [thread overview]
Message-ID: <CAL3q7H6y3-8PhZOiBVxszZV5DN-c81EsQ_NjMaHmgGmJrc9aQA@mail.gmail.com> (raw)
In-Reply-To: <20160120202909.4a804707@natsu>
On Wed, Jan 20, 2016 at 3:29 PM, Roman Mamedov <rm@romanrm.net> wrote:
> Hello,
>
> To reproduce...
>
> *) in one terminal window:
>
> btrfs sub create test
> chattr +C test
> cd test/
> while true; do dd if=/dev/zero of=zerofile bs=1M count=1024; sync; done
>
> *) in another terminal window start repeatedly snapshotting 'test', at random
> 1-3-5 second intervals:
>
> mkdir snaps
> btrfs sub snap test snaps/test-`date +%Y-%m-%dT%H:%M:%S`
>
> The 'dd' output of first window then looks like this for me:
>
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 0.49982 s, 2.1 GB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 0.541291 s, 2.0 GB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 4.88021 s, 220 MB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 4.56427 s, 235 MB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 0.530991 s, 2.0 GB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 5.68497 s, 189 MB/s
> dd: writing `zerofile': No space left on device
> 1+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 0.000591943 s, 0.0 kB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 4.25015 s, 253 MB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 4.66459 s, 230 MB/s
> dd: writing `zerofile': No space left on device
> 1015+0 records in
> 1014+0 records out
> 1063489536 bytes (1.1 GB) copied, 3.0433 s, 349 MB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 4.24264 s, 253 MB/s
> dd: writing `zerofile': No space left on device
> 1+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 0.000647234 s, 0.0 kB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 3.56673 s, 301 MB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 3.71281 s, 289 MB/s
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 0.551317 s, 1.9 GB/s
> ^C
> -----
>
> This also causes my KVM VMs to fail with a high probability during
> snapshotting of their backing subvolume (as described in the previous thread).
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)
>
> --
> With respect,
> Roman
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2016-01-20 20:46 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 [this message]
2016-01-21 9:02 ` Roman Mamedov
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=CAL3q7H6y3-8PhZOiBVxszZV5DN-c81EsQ_NjMaHmgGmJrc9aQA@mail.gmail.com \
--to=fdmanana@gmail.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).