In theory (going by the man page and available documentation, not 100% clear) does the following command indeed actually work as advertised and specify how metadata should be placed and kept only on the "devices" specified after the "-m" flag? Thus given the following example: mkfs.btrfs -L foo -m raid10 <ssd> <ssd> <ssd> <ssd> -d raid10 <rust> <rust> <rust> <rust> Would btrfs stripe/mirror and only keep metadata on the 4 specified SSD devices? Likewise then stripe/mirror and only keep data on the specified 4 spinning rust? In trying and creating this type of setup it appears that data is also being stored on the devices specified as "metadata devices". This is observed through via a "btrfs filesystem show". after committing a large amount of data to the filesystem The data devices have balanced data as expected with plenty of free space but the SSD device are reported as either nearly used or completely used. - DHC -- 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
