Dear Devs,
I have a number of esata disk packs holding 4 physical disks each where
I wish to use the disk packs aggregated for 16TB and up to 64TB backups...
Can btrfs...?
1:
Mirror data such that there is a copy of data on each *disk pack* ?
Note that esata shows just the disks as individual
On Thu, Apr 18, 2013 at 02:45:24PM +0100, Martin wrote:
Dear Devs,
I have a number of esata disk packs holding 4 physical disks each where
I wish to use the disk packs aggregated for 16TB and up to 64TB backups...
Can btrfs...?
1:
Mirror data such that there is a copy of data on each
On 18/04/13 15:06, Hugo Mills wrote:
On Thu, Apr 18, 2013 at 02:45:24PM +0100, Martin wrote:
Dear Devs,
I have a number of esata disk packs holding 4 physical disks each
where I wish to use the disk packs aggregated for 16TB and up to
64TB backups...
Can btrfs...?
1:
Mirror data
On Thu, Apr 18, 2013 at 05:29:10PM +0100, Martin wrote:
On 18/04/13 15:06, Hugo Mills wrote:
On Thu, Apr 18, 2013 at 02:45:24PM +0100, Martin wrote:
Dear Devs,
I have a number of esata disk packs holding 4 physical disks each
where I wish to use the disk packs aggregated for 16TB and
Hugo Mills wrote:
On Thu, Apr 18, 2013 at 02:45:24PM +0100, Martin wrote:
Dear Devs,
snip
Note that esata shows just the disks as individual physical disks, 4 per
disk pack. Can physical disks be grouped together to force the RAID data
to be mirrored across all the nominated groups?
On 18/04/13 20:44, Hugo Mills wrote:
On Thu, Apr 18, 2013 at 05:29:10PM +0100, Martin wrote:
On 18/04/13 15:06, Hugo Mills wrote:
On Thu, Apr 18, 2013 at 02:45:24PM +0100, Martin wrote:
Dear Devs,
I have a number of esata disk packs holding 4 physical disks
each where I wish to use the
On 18/04/13 20:48, Alex Elsayed wrote:
Hugo Mills wrote:
On Thu, Apr 18, 2013 at 02:45:24PM +0100, Martin wrote:
Dear Devs,
snip
Note that esata shows just the disks as individual physical disks, 4 per
disk pack. Can physical disks be grouped together to force the RAID data
to be mirrored
Martin wrote:
snip
Or perhaps include the same Ceph code routines into btrfs?...
That's actually what I was thinking. The CRUSH code is actually already
pretty well factored out - it lives in net/ceph/crush/ in the kernel source
tree, and is treated as part of 'libceph' (which is used by
