On 22/10/2014 14:40, Piotr Pawłow wrote:
On 22.10.2014 03:43, Chris Murphy wrote:
On Oct 21, 2014, at 4:14 PM, Piotr Pawłow<pp@xxxxxxxxxxx> 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.
"Device replace" on raid 0,1,10 works if the device to be replaced is
still alive, otherwise the operation is as long as a rebalance and works
similarly (AFAIR).
Which is way too long in terms of the likelihood of another disk failing.
Additionally, it seeks like crazy during the operation, which also
greatly increases the likelihood of another disk failing.
Until this is fixed I am not confident in using btrfs on a production
system which requires RAID redundancy.
The operation needs to be streamlined: it should be as sequential as
possible (sort files according to their LBA before reading/writing),
with the fewest number of seeks on every disk, and with large buffers,
so that reads from the source disk(s) and writes to the replacement disk
goes at platter-speed or near there.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
