linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kjansen387 <kjansen387@gmail.com>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs freezing on writes
Date: Wed, 15 Apr 2020 13:14:54 +0200	[thread overview]
Message-ID: <920dd953-74b5-2ab5-ed10-7e9d9c18ec26@gmail.com> (raw)
In-Reply-To: <20200411202134.GN2693@hungrycats.org>

OK thanks. I did try 2g on top of 172g, that didn't work, but after 
playing with 'limit' it did, all disks now have 3GB metadata.

On 11-Apr-20 22:21, Zygo Blaxell wrote:

> The purpose of resize -2g was to make a little less unallocated space
> on one drive compared to all the others, starting with all the drives
> having equal unallocated space.  The purpose of resize -172g was to
> make the extra unallocated space on sdd go away, so it would be equal to
> the other 3 drives.  You have to do _both_ of those before the balance.
> Or just add the two numbers, i.e. resize -174g.
> 
> If you really want to be sure, resize by -200g (far more than necessary),
> then balance start -mlimit=4,devid=4.  The balance is "I know there are
> exactly 5 block groups now, and I want to leave exactly one behind,"
> and the resize is "I want no possibility of new block groups on sdd for
> some time."
> 

      reply	other threads:[~2020-04-15 11:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 19:46 btrfs freezing on writes kjansen387
2020-04-07 20:11 ` Chris Murphy
2020-04-07 20:22   ` Chris Murphy
2020-04-07 20:39     ` kjansen387
2020-04-07 22:11       ` Chris Murphy
2020-04-07 22:30         ` kjansen387
2020-04-09  4:32 ` Zygo Blaxell
2020-04-09 21:53   ` kjansen387
2020-04-09 23:07     ` Zygo Blaxell
2020-04-11 19:46       ` kjansen387
2020-04-11 19:59         ` Chris Murphy
2020-04-11 20:21         ` Zygo Blaxell
2020-04-15 11:14           ` kjansen387 [this message]

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=920dd953-74b5-2ab5-ed10-7e9d9c18ec26@gmail.com \
    --to=kjansen387@gmail.com \
    --cc=ce3g8jdj@umail.furryterror.org \
    --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).