On Mon, Aug 10, 2015 at 6:13 AM, Duncan 1i5t5.dun...@cox.net wrote:
We do recommend that you stay relatively current on both kernel and
userspace, however. So a current 4.1 series kernel and btrfs-progs 4.1.2
are excellent, but consider another filesystem if you're the type who was
still on
Hi,
How does btrfs handle raid1 on a bunch of uneven sized disks? Can I
just keep adding arbitrarily sized disks to an existing raid1 and
expect the file system to continue to keep two copies of everything,
so I could survive the loss of any single disk without data loss? Does
btrfs work this
On Sun, Aug 09, 2015 at 02:29:53PM +0200, Jim MacBaine wrote:
Hi,
How does btrfs handle raid1 on a bunch of uneven sized disks? Can I
just keep adding arbitrarily sized disks to an existing raid1 and
expect the file system to continue to keep two copies of everything,
so I could survive the
On Sun, Aug 9, 2015 at 8:47 AM, Hugo Mills h...@carfax.org.uk wrote:
On Sun, Aug 09, 2015 at 02:29:53PM +0200, Jim MacBaine wrote:
Hi,
How does btrfs handle raid1 on a bunch of uneven sized disks? Can I
just keep adding arbitrarily sized disks to an existing raid1 and
expect the file system
Rich Freeman posted on Sun, 09 Aug 2015 22:25:35 -0400 as excerpted:
The key is that btrfs manages raid at the chunk level, not the
device level. When btrfs needs more disk space it allocates a new
chunk from unallocated space on a device. If it is in raid1 mode it
will allocate a pair of
Jim MacBaine posted on Sun, 09 Aug 2015 14:29:53 +0200 as excerpted:
Traditionally I'm using rsync to create hardlinked backups on ext3/4 on
md-raid1. This setup has been working reliably for many years now,
including the survival of two disk failures. But it is quite cumbersome
to reshape
