On 22.10.2014 03:43, Chris Murphy wrote:
On Oct 21, 2014, at 4:14 PM, Piotr Pawłow<p...@siedziba.pl> wrote:
Looks normal to me. Last time I started a balance after adding 6th device to my
FS, it took 4 days to move 25GBs of data.
It's long term untenable. At some point it must be fixed. It's way, way slower
than md raid.
At a certain point it needs to fallback to block level copying, with a ~ 32KB
block. It can't be treating things as if they're 1K files, doing file level
copying that takes forever. It's just too risky that another device fails in
the meantime.
There's "device replace" for restoring redundancy, which is fast, but
not implemented yet for RAID5/6.
I think the problem is that balance was originally used for balancing
data / metadata split - moving stuff out of mostly empty chunks to free
them and use for something else. It pretty much has to be done on the
extent level.
Then balance was repurposed for things like converting RAID profiles and
restoring redundancy and balancing device usage in multi-device
configurations. It works, but the approach to do it extent by extent is
slow.
I wonder if we could do some of these operations by just copying whole
chunks in bulk. Wasn't that the point of introducing logical addresses?
- to be able to move chunks around quickly without changing anything
except updating chunk pointers?
BTW: I'd love a simple interface to be able to select a chunk and tell
it to move somewhere else. I'd like to tell chunks with metadata, or
with tons of extents: Hey, chunks! Why don't you move to my SSDs? :)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
