On 2016-04-27 16:18, Juan Alberto Cirez wrote:
Quick question: Supposed I have n-number of storage pods (physical
servers with n-number of physical hhds). The end deployment will be
btrfs at the brick/block level with a distributed file system on top.
Keeping in mind that my overriding goal is to have high availability
and the mechanism whereby the lost of a drive or multiple drives in a
single pod will not jeopardize data.
Question<<<<<
Does partitioning the physical drives and creating btrfs filesystem on
each partition, then configuring each partition as individual
bricks/blocks offer ANY added benefits over grouping the entire pod
into a drive pool and using that pool as a single block/brick to
expose to the distributed filesystem?
This overall depends on a number of factors. From a data safety issue,
I'd say grouping drives pair-wise in each server with BTRFS raid1 would
be the best option if you absolutely want to use BTRFS.
I somewhat agree with Chris Murphy's statement that you may not want to
use BTRFS because it's still relatively new, but I'm more of the opinion
that as long as you're following the usual sysadmin rules (do proper
research, test thoroughly, keep backups, and don't upgrade everything at
once if at all possible) and are using stuff that's been around for a
while (like raid1 mode inst4ead of one of the parity modes), you should
generally be fine. If you do go with BTRFS, I'd suggest subscribing to
the mailing list and ideally practicing fixing broken filesystems.
--
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
