From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Martin Raiber <martin@urbackup.org>
Subject: Re: strange No space left on device issues
Date: Thu, 20 Jul 2017 23:33:56 +0200 [thread overview]
Message-ID: <1500586436.7266.18.camel@scientia.net> (raw)
In-Reply-To: <20170720173214.GA29924@vader.DHCP.thefacebook.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Thu, 2017-07-20 at 10:32 -0700, Omar Sandoval wrote:
> If that doesn't work, could you please also try
> https://patchwork.kernel.org/patch/9829593/?
Okay, tried the patch now, applied upon:
Linux 4.12.0-trunk-amd64 #1 SMP Debian 4.12.2-1~exp1 (2017-07-18) x86_64 GNU/Linux
(that is the Debian source package, with all their further patches and
their kernel config).
with the parameters at their defaults:
# sysctl vm.dirty_bytes
vm.dirty_bytes = 0
# sysctl vm.dirty_background_bytes
vm.dirty_background_bytes = 0
Tried copying the whole image three times (before I haven had a single
copy of the whole image with at least one error, so that should be
"proof" enough that it fixes the isse) upon the btrfs fs,... no errors
this time...
Looks good :-)
I assume you'll take care to get that patch into stable kernels?
Is this patch alone enough to recommend the Debian maintainers to
include it into their 4.9 long term stable kernels?
And would you recommend this as an "urgent" fix?
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2017-07-20 21:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 14:39 strange No space left on device issues Christoph Anton Mitterer
2017-07-20 14:44 ` Christoph Anton Mitterer
[not found] ` <0102015d6083ffde-e6d15fd5-6e66-41a0-9ddf-af163c96ebd8-000000@eu-west-1.amazonses.com>
2017-07-20 15:20 ` Christoph Anton Mitterer
2017-07-20 15:20 ` Christoph Anton Mitterer
2017-07-20 17:32 ` Omar Sandoval
2017-07-20 17:48 ` Christoph Anton Mitterer
2017-07-20 17:55 ` Omar Sandoval
2017-07-20 18:06 ` Christoph Anton Mitterer
2017-07-20 18:14 ` Omar Sandoval
2017-07-20 20:28 ` Christoph Anton Mitterer
2017-07-20 21:19 ` Omar Sandoval
2017-07-20 21:33 ` Christoph Anton Mitterer [this message]
2017-07-20 21:48 ` Omar Sandoval
2017-07-20 21:53 ` Christoph Anton Mitterer
2017-07-20 21:59 ` Omar Sandoval
2017-07-20 22:02 ` Hans van Kranenburg
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=1500586436.7266.18.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@urbackup.org \
--cc=osandov@osandov.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).