On Sun, Mar 10, 2013 at 11:24 PM, Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: >> On 03/09/2013 09:31 PM, Hugo Mills wrote: >> > Some time ago, and occasionally since, we've discussed altering the >> > "RAID-n" terminology to change it to an "nCmSpP" format, where n is the >> > number of copies, m is the number of (data) devices in a stripe per copy, >> > and p is the number of parity devices in a stripe. >> > > > Hugo. > > -- > === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === > PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk > --- Great oxymorons of the world, no. 6: Mature Student --- It's important that the userland tools will output the things in both a 'human readable' format as well as the short forms. I would say when giving btrfs a parameter, it should only accept the short forms. But in order to allow users to figure out what they actually mean when doing something like 'btrfs fi show' it should tell you sometihng by the lines of '1 copy, 3 stripes, 1 parity (1C3S1P)' instead of just the short form. I would also make the case that leaving out 'defaults' from the output is bad for the learning curve as well. Even when it's just 1C I wouldn't remove that from the output, but the input parameter when you work with it should know what you mean when you leave 1C out, of course, and not require it. -- 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
