public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: Automatic balance after mkfs?
Date: Tue, 16 Jun 2015 09:21:44 -0400	[thread overview]
Message-ID: <558022E8.7070201@gmail.com> (raw)
In-Reply-To: <pan.2015.06.16.13.13.40@googlemail.com>

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

On 2015-06-16 09:13, Holger Hoffstätte wrote:
>
> Forking from the other thread..
>
> On Tue, 16 Jun 2015 12:25:45 +0000, Hugo Mills wrote:
>
>>     Yes. It's an artefact of the way that mkfs works. If you run a
>> balance on those chunks, they'll go away. (btrfs balance start
>> -dusage=0 -musage=0 /mountpoint)
>
> Since I had to explain this very same thing to a new btrfs-using friend
> just yesterday I wondered if it might not make sense for mkfs to issue
> a general balance after creating the fs? It should be simple enough
> (just issue the balance ioctl?) and not have any negative side effects.
>
> Just doing such a post-mkfs cleanup automatically would certainly
> reduce the number of times we have to explain the this. :)
>
> Any reasons why we couldn't/shouldn't do this?
>
Following the same line of thinking, is there any reason we couldn't 
just rewrite mkfs to get rid of this legacy behavior?



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]

  reply	other threads:[~2015-06-16 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 13:13 Automatic balance after mkfs? Holger Hoffstätte
2015-06-16 13:21 ` Austin S Hemmelgarn [this message]
2015-06-18  5:41   ` Qu Wenruo
2015-06-26 13:44     ` David Sterba
2015-06-16 13:24 ` 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=558022E8.7070201@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=holger.hoffstaette@googlemail.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