Re: [PATCH] Btrfs-progs: replace find_mount_root from send code
From: Alex Lyakas <hidden>
Date: 2012-08-27 09:16:37
Hi Robert, do you think you can make the "root_snap_send" file of yours available anywhere (not sure how big it is)? Also, I am not sure I understand how you btrfs tree looks like WRT to where all subvolumes are mounted (but all others seem to understand well). You mentioned:
/dev/loop0 on /mnt/TEST_ROOT type btrfs (rw,relatime,compress=lzo,space_cache) # default-subvolume /dev/loop0 on /mnt/TEST_ROOT/root_volid0 type btrfs (rw,relatime,compress=lzo,space_cache) # subvolid= 0 /dev/loop1 on /mnt/TEST_ROOT/backup_volid0 type btrfs (rw,relatime,compress=lzo,space_cache)
btrfs subvolume snapshot -r /mnt/TEST_ROOT/root_volid0/root/ /mnt/TEST_ROOT/root_volid0/root_snap
Are you trying to snapshot a directory here? I.e., what is "root" within "root_volid0"? Can you pls list all subvolumes you have on your source filesystem (the one you are trying to backup), and where each one is mounted? Again, looks like I'm the only one confused about this, so apologies. You can also possibly use the "tree" utility to better visualize your fs tree, like: tree -A --inodes --noreport /mnt/TEST_ROOT Jan, David, hope it's ok with you if I'll try to debug this. Thanks, Alex. On Sat, Aug 25, 2012 at 11:24 AM, Robert Buhren [off-list ref] wrote:
On 24.08.2012 15:33, David Sterba wrote:quoted
On Thu, Aug 23, 2012 at 10:54:54AM +0200, Robert Buhren wrote:quoted
I'm on linux-3.6-rc2 and btrfs-progs from git.Please try it with Chris' for-linus branch, it contains a fair portion of send-related fixes and from brief look they may be related to the errors you see. davidHi David, i just tried it with a kernel from the "for-linus" branch. But i still get the same error. Just to be sure: You ment this branch: http://git.kernel.org/?p=linux/kernel/git/mason/linux-btrfs.git;a=shortlog;h=refs/heads/for-linus right? Regards, Robert -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html