On Apr 20, 2014, at 11:27 AM, Adam Brenner <adam@xxxxxx> wrote: > > mkfs.btrfs -d single /dev/sda3 /dev/sdb /dev/sdc -f > > Once setup, I transferred roughly 3.1TB of data and noticed the write speed was limited to 200MB/s. This is the same write speed that I would see across a single device. I used dd with oflag=direct and a block size of 1M and a count of 1024 from /dev/zero. Both showed the same speeds. This is expected. And although I haven't tested it, I think you'd get the same results with multiple threads writing at the same time: the allocation would aggregate the threads to one chunk at a time until full, which means writing to one device at a time, then writing a new chunk on a different device until full, and so on in round robin fashion. I also haven't tested this, so I'm not sure if different behavior happens for reading files located in different chunks on different devices, if those are effectively single threaded reads, or if the files can be read simultaneously. > > So my question is, should I have setup the BTRFS filesystem with -d raid0? Would this have worked with multiple devices with different sizes? raid0 does work with multiple devices of different sizes, but it won't use the full capacity of the last drive with the most space. For example: 2GB, 3GB, and 4GB devices as raid0. The first 2GB copies using 3 stripes, one per device, until the 2GB device is full. The next 1GB copies using 2 stripes, one per remaining device (the 3GB and 4GB ones) until the 3GB device is full. Additional copying results in "cp: error writing ‘./IMG_2892.dng’: No space left on device" Label: none uuid: 7dfde9eb-04a8-4920-95c0-51253b2483f8 Total devices 3 FS bytes used 7.33GiB devid 1 size 2.00GiB used 2.00GiB path /dev/sdb devid 2 size 3.00GiB used 3.00GiB path /dev/sdc devid 3 size 4.00GiB used 3.00GiB path /dev/sdd Ergo, there is no such thing as single device raid0, so the point at which all but 1 drive is full, writes fail. Chris Murphy -- 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
