Hugo Mills posted on Sun, 04 May 2014 19:31:55 +0100 as excerpted: > My proposal was simply a description mechanism, not an > implementation. The description is N-copies, M-device-stripe, > P-parity-devices (NcMsPp), and (more or less comfortably) covers at > minimum all of the current and currently-proposed replication levels. > There's a couple of tweaks covering description of allocation rules > (DUP vs RAID-1).
Thanks. That was it. =:^) But I had interpreted the discussion as a bit more concrete in terms of ultimate implementation than it apparently was. Anyway, it would indeed be nice to see an eventual implementation such that the above notation could be used with, for instance, mkfs.btrfs, and btrfs balance start -Xconvert, but regardless, that does look to be a way off. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
