On Mon, 2015-12-28 at 01:58 +0000, Hugo Mills wrote: > Isn't this an FAQ already? There is already a patch to rename the > RAID modes. It's been sitting in the progs patch queue for about 2 > years, because none of the senior devs has acked it yet (since it's a > big user-visible change). Uhm... yeah, it's a bit invasive... but that happens when such improper naming is done in the first place :-/ It's similar to when tools wrongly or ambiguously use SI prefixes, instead of proper kB, MB, GB, etc. (for base 1000) respectively KiB, MiB, GiB, etc. (for base 1024). Especially just using K,M,G, is simply evil and should lead to public punishment ;-) I'm also not really fond of what btrfs took over from LVM, namely kKmMgGtTpPeE,... it's ambiguous or at least unclean as well... Best would be probably if we don't use "raid" as names at all (or just as aliases for the actual canonical names), but rather describe what's actually... E.g. classic RAID1 = mirror btrfs RAID1 = dup2 or something similar like clone2, replica2 classic RAID0 = striped RAID5/6 = parityN Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
