linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 20:06:52 +0200	[thread overview]
Message-ID: <1500574012.7266.13.camel@scientia.net> (raw)
In-Reply-To: <20170720175551.GB29924@vader.DHCP.thefacebook.com>

[-- Attachment #1: Type: text/plain, Size: 346 bytes --]

On Thu, 2017-07-20 at 10:55 -0700, Omar Sandoval wrote:
> Against 4.12 would be best, thanks!
okay,.. but that will take a while to compile...


in the meantime... do you know whether it's more or less safe to use
the 4.9 kernel without any fix, when I change the parameters mentioned
before, during the massive copying?

Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]

  reply	other threads:[~2017-07-20 18:06 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 [this message]
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
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=1500574012.7266.13.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).