Hi Stephan,
I fully understand the first part of your fix, and I believe it's
quite critical. Indeed, a writable snapshot should have no evidence
that it has an ancestor that was once received.
Can you pls let me know that I understand the second part of your fix.
In btrfs-progs the following
As for splitting a leaf, root is just the leaf, and tree mod log does not apply
on leaf, so in this case, we don't do log_removal.
As for splitting a node, the old root is kept as a normal node and we have
nicely
put records in tree mod log for moving keys and items, so in this case we don't
do
During splitting a leaf, pushing items around to hopefully get some space only
works when we have a parent, ie. we have at least one sibling leaf.
Signed-off-by: Liu Bo bo.li@oracle.com
---
fs/btrfs/ctree.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Hi,
I have setup about a year ago a BTRFS RAID 1 filesystem on two 2TB
Western Digital WD20EARS hard drives and I have created subvolumes
that I mount regularly as I need them. I put mostly music, videos and
various files on them as well as some Git bare repositories for my
work files but for
On Wed, May 22, 2013 at 07:22:42AM -0600, Laurent Humblet wrote:
Hi,
I have setup about a year ago a BTRFS RAID 1 filesystem on two 2TB
Western Digital WD20EARS hard drives and I have created subvolumes
that I mount regularly as I need them. I put mostly music, videos and
various files on
On 19/05/13 18:32, Martin wrote:
Dear Devs,
Would there be any problem to use nbd (/dev/ndX) devices to gain
btrfs-raid across multiple physical hosts across a network? (For a sort
of btrfs-drbd! :-) )
Regards,
Martin
http://en.wikipedia.org/wiki/Network_block_device
