linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs convert running out of space
Date: Tue, 20 Jan 2015 00:38:31 -0700	[thread overview]
Message-ID: <CAJCQCtRe+0n84PUZuWKw0UUwK_RF_AhW4sMZ+07r96qaNvRWKg@mail.gmail.com> (raw)
In-Reply-To: <CA+WRLO8gGUxxHhqQfgQWXyU0kT2=nf7u5oPFYJTWY=hSMNBj=w@mail.gmail.com>

> On Mon, Jan 19, 2015 at 5:13 PM, Gareth Pye <gareth@cerberos.id.au> wrote:
> I just tried from a slightly different tack, after doing another
> -dusage=2 pass I did the following:
> # btrfs balance start -v -dconvert=raid1 -dsoft -dusage=96 /data
> Dumping filters: flags 0x1, state 0x0, force is off
>   DATA (flags 0x302): converting, target=16, soft is on, usage=96
> Done, had to relocate 0 out of 3763 chunks
> # btrfs balance start -v -dconvert=raid1 -dsoft -dusage=99 /data
> Dumping filters: flags 0x1, state 0x0, force is off
>   DATA (flags 0x302): converting, target=16, soft is on, usage=99
> ERROR: error during balancing '/data' - No space left on device


I guess I don't really understand the purpose of combining dconvert
and dusage. Sure, it should either work or give an error, so there may
still be a bug here. But I'm just not following why they'd be used
together, seems superfluous. What happens when they're tried
separately? I'm not sure which one's instigating the problem.

Also I think you should upgrade to btrfs-progs 3.18, seeing as 3.12 is
old and if there's a bug in that version of progs vs the kernel, it's
not going to get fixed.



-- 
Chris Murphy

  parent reply	other threads:[~2015-01-20  7:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 23:45 btrfs convert running out of space Gareth Pye
2015-01-20  0:13 ` Gareth Pye
2015-01-20  5:39   ` Lakshmi_Narayanan_Du
2015-01-20  7:38   ` Chris Murphy [this message]
2015-01-20 21:25     ` Gareth Pye
2015-01-20 21:41       ` Chris Murphy
2015-01-20 21:49         ` Gareth Pye
2015-01-20 22:53           ` Chris Murphy
2015-01-20 23:04             ` Gareth Pye
2015-01-21  4:03               ` Chris Murphy
2015-01-22 21:58                 ` Gareth Pye
2015-01-22 21:58                   ` Gareth Pye
2015-01-23  4:34                   ` Duncan
2015-01-23  7:54                     ` Marc Joliet
2015-01-23  8:46                       ` Duncan
2015-01-25 15:23                         ` Marc Joliet
2015-01-27  3:24                           ` Gareth Pye
2015-01-27  6:20                             ` Duncan
2015-01-27 21:53                               ` Gareth Pye
2015-01-28  0:18                                 ` Duncan
2015-01-20 23:33         ` Hugo Mills

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=CAJCQCtRe+0n84PUZuWKw0UUwK_RF_AhW4sMZ+07r96qaNvRWKg@mail.gmail.com \
    --to=lists@colorremedies.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).