Hey Chris,
On 02/02/2013 05:02 PM, Chris Mason wrote:
Btrfs -- 604MB/s
MD-- 162MB/s
MD -- 800MB/s very little system time
Btrfs -- 3.8GB/s one CPU mostly pegged
Btrfs -- 380MB/s seen by fio
MD-- 174MB/s seen by fio
Creating 12 million files on Btrfs raid5 took 226 seconds, vs
On Tue, Feb 12, 2013 at 08:16:49AM -0700, Kaspar Schleiser wrote:
Hey Chris,
On 02/02/2013 05:02 PM, Chris Mason wrote:
Btrfs -- 604MB/s
MD-- 162MB/s
MD -- 800MB/s very little system time
Btrfs -- 3.8GB/s one CPU mostly pegged
Btrfs -- 380MB/s seen by fio
MD--
On Sun, Feb 10, 2013 at 03:35:05PM -0700, Gordon Manning wrote:
Hi,
Is the BTRFS raid code susceptible to RAID-5 write holes? �I think with
the original plan, the problem was avoided by always giving full stripe
writes to the raid layers. �Does the current plan deal with the hole
Hi,
I believe XOR_BLOCKS must be selected, otherwise build fails with:
ERROR: xor_blocks [fs/btrfs/btrfs.ko] undefined!
diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig
index 4f5dc93..5f583c8 100644
--- a/fs/btrfs/Kconfig
+++ b/fs/btrfs/Kconfig
@@ -7,6 +7,7 @@ config BTRFS_FS
select
On Tue, Feb 05, 2013 at 07:22:36AM -0700, Tomasz Torcz wrote:
Hi,
I believe XOR_BLOCKS must be selected, otherwise build fails with:
ERROR: xor_blocks [fs/btrfs/btrfs.ko] undefined!
diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig
index 4f5dc93..5f583c8 100644
--- a/fs/btrfs/Kconfig
@@ -1389,6 +1392,14 @@ int btrfs_rm_device(struct btrfs_root *root, char
*device_path)
}
btrfs_dev_replace_unlock(root-fs_info-dev_replace);
+ if ((all_avail (BTRFS_BLOCK_GROUP_RAID5 |
+ BTRFS_BLOCK_GROUP_RAID6) num_devices = 3)) {
+
On Mon, Feb 04, 2013 at 02:42:24PM -0700, H. Peter Anvin wrote:
@@ -1389,6 +1392,14 @@ int btrfs_rm_device(struct btrfs_root *root, char
*device_path)
}
btrfs_dev_replace_unlock(root-fs_info-dev_replace);
+ if ((all_avail (BTRFS_BLOCK_GROUP_RAID5 |
+
Also, a 2-member raid5 or 3-member raid6 are a raid1 and can be treated as such.
Chris Mason chris.ma...@fusionio.com wrote:
On Mon, Feb 04, 2013 at 02:42:24PM -0700, H. Peter Anvin wrote:
@@ -1389,6 +1392,14 @@ int btrfs_rm_device(struct btrfs_root *root,
char
*device_path)
}
I felt like having a small play with this stuff, as I've been wanting
it for so long :)
But apparently I've made some incredibly newb error.
I used the following two lines to check out the code:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
raid56-experimental
git
The last argument should be the directory you want to clone into. Use
'-b branch' to specify the branch you want to clone. I'm pretty sure
you've compiled just the master branch of both linux-btrfs and
btrfs-progs.
On Mon, Feb 4, 2013 at 8:59 PM, Gareth Pye gar...@cerberos.id.au wrote:
I felt
Thank you, that makes a lot of sense :)
It's been a good day, I've learnt something :)
On Tue, Feb 5, 2013 at 4:29 PM, Chester somethingsome2...@gmail.com wrote:
The last argument should be the directory you want to clone into. Use
'-b branch' to specify the branch you want to clone. I'm
Hi Chris,
I've been keen for raid5/6 in btrfs since I heard of it.
I cannot give you any feedback, but I'd like to take the opportunity to
thank you -and all contributors (thinking of David for the raid) for
your work.
Regards,
Hendrik
--
To unsubscribe from this list: send the line
Hi everyone,
I've uploaded an experimental release of the raid5/6 support to git, in
branches named raid56-experimental. This is based on David Woodhouse's
initial implementation (thanks Dave!).
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
raid56-experimental
13 matches
Mail list logo
