All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Automatic balance after mkfs?
Date: Tue, 16 Jun 2015 13:24:33 +0000	[thread overview]
Message-ID: <20150616132433.GJ9850@carfax.org.uk> (raw)
In-Reply-To: <pan.2015.06.16.13.13.40@googlemail.com>

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

On Tue, Jun 16, 2015 at 01:13:40PM +0000, 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.

   Mount, balance, unmount... You can't balance on an unmounted FS.
You'd also have to write something to the FS (see below).

> 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?

   On an empty filesystem, it used to throw away the RAID
configuration, which was identified from the existing chunks on the
FS. With no chunks remaining, the RAID configuration reverted to
single all round (IIRC). I don't know if that's been fixed since those
days, but it's something to be wary of, at the very least.

   I've added the question as an entry to the FAQ, anyway.

   Hugo.

-- 
Hugo Mills             | vi vi vi: the Editor of the Beast.
hugo@... carfax.org.uk |
http://carfax.org.uk/  |
PGP: E2AB1DE4          |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2015-06-16 13:24 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
2015-06-18  5:41   ` Qu Wenruo
2015-06-26 13:44     ` David Sterba
2015-06-16 13:24 ` Hugo Mills [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=20150616132433.GJ9850@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --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 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.