The 65k stripe length should be ignored as the stripes are
physically contiguous on disk so transfers can span stripes.
Signed-off-by: jim owens jow...@hp.com
---
fs/btrfs/volumes.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/volumes.c
Our set/get functions for compat_ro_flags actually look at compat_flags. This
will mess any attempt to use compat flags up. The fix is obvious. Thanks,
Signed-off-by: Josef Bacik jo...@redhat.com
---
fs/btrfs/ctree.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On Thu, Dec 17, 2009 at 04:40:24PM -0500, Josef Bacik wrote:
This is just to mark the fs that it's been tinkered with to set the default
subvolume. It's a compatible change because older kernels will just ignore
the
default setting and mount the same thing they always have. Thanks,
I
Returning a value greater than the caller's is ugly and prone
to dangerous future coding mistakes.
Signed-off-by: jim owens jow...@hp.com
---
fs/btrfs/extent-tree.c |3 ---
fs/btrfs/inode.c |5 ++---
fs/btrfs/volumes.c |9 +
3 files changed, 7 insertions(+), 10
Hello everyone,
This btrfs update is mostly a collection of fixes. Josef has the
snapshot-supported yum update code pending, but I wanted to give that
some more time to cook before we send it out.
Linus please pull the for-linus branch of the btrfs-unstable tree
Older kernels would generally be able to still mount the filesystem with the
default subvolume set, but it would result in a different volume being mounted,
which could be an even more unpleasant suprise for users. So if you set your
default subvolume, you can't go back to older kernels. Thanks,
WRITE is needed on btrfs_map_block() to fetch all raid stripes,
READ only returns one device and we want to discard all copies.
Signed-off-by: jim owens jow...@hp.com
---
fs/btrfs/extent-tree.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/btrfs/extent-tree.c
Use simple struct operation instead of address calculation.
Signed-off-by: Zhao Lei zhao...@cn.fujitsu.com
---
fs/btrfs/ctree.h | 46 ++
1 files changed, 14 insertions(+), 32 deletions(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index
2009/12/18 Zhaolei zhao...@cn.fujitsu.com:
sniper wrote:
No, many pointers in btrfs function arguments are not pointing to an
absolute address, but relative to the start address of extent.
Take following function as example, argument inode_item is an offset
value to the beginning of leaf. So
