On Apr 21, 2014, at 3:09 PM, Duncan 1i5t5.dun...@cox.net wrote:
Adam Brenner posted on Sun, 20 Apr 2014 21:56:10 -0700 as excerpted:
So ... BTRFS at this point in time, does not actually stripe the data
across N number of devices/blocks for aggregated performance increase
(both read and
On Tue, Apr 22, 2014 at 11:42:09AM -0600, Chris Murphy wrote:
On Apr 21, 2014, at 3:09 PM, Duncan 1i5t5.dun...@cox.net wrote:
Adam Brenner posted on Sun, 20 Apr 2014 21:56:10 -0700 as excerpted:
So ... BTRFS at this point in time, does not actually stripe the data
across N number of
On Apr 22, 2014, at 11:56 AM, Hugo Mills h...@carfax.org.uk wrote:
Also not helped by btrfs's co-option of the term RAID-1 to mean
something that's not traditional RAID-1, and (internally) stripe and
chunk to mean things that don't match (I think) any of the
definitions above…
Right.
Chris Murphy posted on Tue, 22 Apr 2014 11:42:09 -0600 as excerpted:
On Apr 21, 2014, at 3:09 PM, Duncan 1i5t5.dun...@cox.net wrote:
Adam Brenner posted on Sun, 20 Apr 2014 21:56:10 -0700 as excerpted:
So ... BTRFS at this point in time, does not actually stripe the
data across N number
Adam Brenner posted on Sun, 20 Apr 2014 21:56:10 -0700 as excerpted:
So ... BTRFS at this point in time, does not actually stripe the data
across N number of devices/blocks for aggregated performance increase
(both read and write)?
What Chris says is correct, but just in case it's unclear as
Howdy,
I recently setup a new BTRFS filesystem based on BTRFS version 3.12 on
Linux kernel 3.13-1 running Debian Jessie.
The BTRFS volume spans 3x 4TB disks, two of which are using the entire
raw block device, and one of them is using a partition (OS disks). The
setup is like so:
On Apr 20, 2014, at 11:27 AM, Adam Brenner a...@aeb.io wrote:
mkfs.btrfs -d single /dev/sda3 /dev/sdb /dev/sdc -f
Once setup, I transferred roughly 3.1TB of data and noticed the write speed
was limited to 200MB/s. This is the same write speed that I would see across
a single device.
On Apr 20, 2014, at 2:54 PM, Chris Murphy li...@colorremedies.com wrote:
Ergo, there is no such thing as single device raid0, so the point at which
all but 1 drive is full, writes fail.
Correction. Data writes fail. Metadata writes apparently still succeed, as zero
length files are
On 04/20/2014 01:54 PM, Chris Murphy wrote:
This is expected. And although I haven't tested it, I think you'd get
the same results with multiple threads writing at the same time: the
allocation would aggregate the threads to one chunk at a time until
full, which means writing to one device at a
On Apr 20, 2014, at 10:56 PM, Adam Brenner a...@aeb.io wrote:
On 04/20/2014 01:54 PM, Chris Murphy wrote:
This is expected. And although I haven't tested it, I think you'd get
the same results with multiple threads writing at the same time: the
allocation would aggregate the threads to one
10 matches
Mail list logo
