All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
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 14:19:40 -0700	[thread overview]
Message-ID: <20170720211940.GD29924@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <1500582495.7266.16.camel@scientia.net>

On Thu, Jul 20, 2017 at 10:28:15PM +0200, Christoph Anton Mitterer wrote:
> On Thu, 2017-07-20 at 11:14 -0700, Omar Sandoval wrote:
> > Yes, that's a safe enough workaround. It's a good idea to change the
> > parameters back after the copy.
> you mean even without having the fix, right?

Yes, even without the fix you should be okay.

> So AFAIU, the bug doesn't really cause FS corruption, but just "false"
> ENOSPC and these happen during having meta-data creating (e.g. during
> operations like mine) only?

Right.

  reply	other threads:[~2017-07-20 21:19 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 [this message]
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=20170720211940.GD29924@vader.DHCP.thefacebook.com \
    --to=osandov@osandov.com \
    --cc=calestyo@scientia.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin@urbackup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.