I've gone ahead and created a single drive Btrfs filesystem on a 3TB drive and started copying content from a raid5 array to the Btrfs volume. Initially copy speeds were very good sustained at ~145MB/s and I left it to run overnight. This morning I ran btrfs fi usage /mnt/btrfs and it reported around 700GB free. I selected another folder containing 204GB and started a copy operation, again from the raid5 array to the Btrfs volume. Copying is now materially slower and slowing further...it started at ~105MB/s and after 141GB has slowed to around 97MB/s. Is this to be expected with Btrfs of have I come across a bug of some sort?
On Sat, Nov 14, 2015 at 12:43 PM, audio muze <audiom...@gmail.com> wrote: > I'm looking to make a "production copy" of my music and video library > for use in our media server. It is not my intent to create any form > of RAID array, but rather to treat each drive independently where > filesystem is concerned and then to create a single view of the drives > using mhddfs. As the data will remain relatively static I may also > deploy Snapraid in conjunction with mhddfs. > > I'm considering using Btrfs as the underlying filesystem on each of > the individual drives, principally to take advantage of metadata > redundancy. Am I corect in surmising that ?I can turn checksumming > off given it's of no utility where a Btrfs volume is comprised of a > single device only? -- 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
