Austin S Hemmelgarn wrote on 2015/06/16 09:21 -0400:
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?
Compared to the more complex auto balance, rewrite mkfs is a much better
idea.
The original mkfs seems easy for developers, but bad for users.
I like the idea and I'll try to implment it if I have spare time.
Thanks.
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
