So i made a filesystem image
$ dd if=/dev/zero of=root_fs bs=1024 count=$(expr 1024 \* 1024)
$ mkfs.btrfs root_fs
Then I put some debian on it (my kernel is 2.6.35-27-generic #48-Ubuntu)
$ mkdir root
$ mount -o loop root_fs root
$ debootstrap sid root
$ umount root
Then i run uml...
* Ken Drummond (bt...@kendrummond.com) [110402 11:51]:
> I don't really understand the details here, but doesn't the creation of
> a snapshot already lead to data extents being shared between
> sub-volumes? From a simple user perspective this sounds like a very
> useful capability.
I was surprise
Signed-off-by: Larry D'Anna
---
fs/btrfs/ctree.c| 28 ++--
fs/btrfs/ctree.h|2 +-
fs/btrfs/dir-item.c |2 +-
fs/btrfs/extent-tree.c | 74
fs/btrfs/file-item.c| 12 +++---
fs/btrfs/f
Signed-off-by: Larry D'Anna
---
fs/btrfs/ioctl.c | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index f9717b6..10095c7 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -1804,6 +1804,7 @@ static noinline
is by cp -a --reflink=always all the files found in the UML
slackware root_fs, and also by cloning a test file with hundreds of
random extents and holes.
Larry D'Anna (2):
btrfs: remove unused argument 'root' from btrfs_release_path
btrfs: allow cross-subvolume BTRFS_IOC_CLON
