Running a traditional raid5 array of that size is statistically guaranteed to fail in the event of a rebuild. I also need to expand the size of available storage to accomodate future storage requirements. My understanding is that a Btrfs array is easily expanded without the overhead associated with expanding a traditional array. Add to that the ability to throw varying drive sizes at the problem and a Btrfs RAID array looks pretty appealing.
For clarity, my intention is to create a Btrfs array using new drives, not to convert the existing ext4 raid5 array. On Wed, Aug 26, 2015 at 2:03 PM, Austin S Hemmelgarn <ahferro...@gmail.com> wrote: > On 2015-08-26 07:50, Roman Mamedov wrote: >> >> On Wed, 26 Aug 2015 10:56:03 +0200 >> George Duffield <forumscollect...@gmail.com> wrote: >> >>> I'm looking to switch from a 5x3TB mdadm raid5 array to a Btrfs based >>> solution that will involve duplicating a data store on a second >>> machine for backup purposes (the machine is only powered up for >>> backups). >> >> >> What do you want to achieve by switching? As Btrfs RAID5/6 is not safe >> yet, do >> you also plan to migrate to RAID10, losing in storage efficiency? >> >> Why not use Btrfs in single-device mode on top of your mdadm RAID5/6? Can >> even >> migrate without moving any data if you currently use Ext4, as it can be >> converted to Btrfs in-place. >> > As of right now, btrfs-convert does not work reliably or safely. I would > strongly advise against using it unless you are trying to help get it > working again. > -- 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
