Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-21 Thread Jeff Mahoney
On 11/19/13, 12:12 AM, deadhorseconsulting wrote: In theory (going by the man page and available documentation, not 100% clear) does the following command indeed actually work as advertised and specify how metadata should be placed and kept only on the devices specified after the -m flag?

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-20 Thread Hugo Mills
On Tue, Nov 19, 2013 at 11:16:58PM +, Duncan wrote: Hugo Mills posted on Tue, 19 Nov 2013 09:06:02 + as excerpted: This will happen with RAID-10. The allocator will write stripes as wide as it can: in this case, the first stripes will run across all 8 devices, until the SSDs are

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-20 Thread Chris Murphy
On Nov 19, 2013, at 11:35 PM, Martin m_bt...@ml1.co.uk wrote: On 19/11/13 23:16, Duncan wrote: So we have: 1) raid1 is exactly two copies of data, paired devices. 2) raid0 is a stripe exactly two devices wide (reinforced by to read a stripe takes only two devices), so again paired

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-20 Thread Russell Coker
On Wed, 20 Nov 2013, Chris Murphy li...@colorremedies.com wrote: Hot spares are worse than useless. Especially for raid10. The drive takes up space doing nothing but suck power, rather than adding space or performance. Somehow this idea comes from cheap companies who seem to think their data

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-20 Thread Hugo Mills
On Wed, Nov 20, 2013 at 04:43:57PM +, Duncan wrote: Hugo Mills posted on Wed, 20 Nov 2013 08:09:58 + as excerpted: RAID-0: min 2 devices RAID-10: min 4 devices RAID-5: min 2 devices (I think) RAID-6: min 3 devices (I think) RAID-5 should be 3-device minimum (each stripe

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-20 Thread Duncan
Hugo Mills posted on Wed, 20 Nov 2013 16:52:47 + as excerpted: Perhaps it's time I get that wiki account and edit some of this stuff myself... Do check the assumptions first. :) Of course. =:^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-19 Thread Hugo Mills
On Mon, Nov 18, 2013 at 11:12:03PM -0600, deadhorseconsulting wrote: In theory (going by the man page and available documentation, not 100% clear) does the following command indeed actually work as advertised and specify how metadata should be placed and kept only on the devices specified

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-19 Thread deadhorseconsulting
Interesting, this confirms what I was observing. Given the wording in man pages for -m and -d which states Specify how the metadata or data must be spanned across the devices specified. I took devices specified to literally mean the devices specified after the according switch. - DHC On Tue,

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-19 Thread Duncan
deadhorseconsulting posted on Tue, 19 Nov 2013 13:24:01 -0600 as excerpted: Interesting, this confirms what I was observing. Given the wording in man pages for -m and -d which states Specify how the metadata or data must be spanned across the devices specified. I took devices specified to

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-19 Thread Duncan
Hugo Mills posted on Tue, 19 Nov 2013 09:06:02 + as excerpted: This will happen with RAID-10. The allocator will write stripes as wide as it can: in this case, the first stripes will run across all 8 devices, until the SSDs are full, and then will write across the remaining 4 devices.

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-19 Thread Martin
On 19/11/13 23:16, Duncan wrote: So we have: 1) raid1 is exactly two copies of data, paired devices. 2) raid0 is a stripe exactly two devices wide (reinforced by to read a stripe takes only two devices), so again paired devices. Which is fine for some occasions and a very good start

Re: Actual effect of mkfs.btrfs -m raid10 /dev/sdX ... -d raid10 /dev/sdX ...

2013-11-19 Thread Martin
On 19/11/13 19:24, deadhorseconsulting wrote: Interesting, this confirms what I was observing. Given the wording in man pages for -m and -d which states Specify how the metadata or data must be spanned across the devices specified. I took devices specified to literally mean the devices