From: Arne Jansen <sensille@gmx.net>
To: Robert Buhren <robert@robertbuhren.de>
Cc: linux-btrfs@vger.kernel.org, Alexander Block <ablock84@googlemail.com>
Subject: Re: Testing new send/receive: "ERROR: could not resolve root_id for"
Date: Sun, 19 Aug 2012 16:59:24 +0200 [thread overview]
Message-ID: <5030FF4C.8080103@gmx.net> (raw)
In-Reply-To: <5028D57F.5090803@robertbuhren.de>
The problem here is that you nest multiple mounts of the same fs.
This confuses find_mount_root which determines the upper-level
mount as the mountpoint instead of the lower-level one.
It does that because it searches upwards for the first change in
the fsid. As you nested the name fs, the fsid does not change when
it crosses the boundary, so it misses the mountpoint.
What is the accepted way to find a mountpoint? I've seen lots of
code that searches the mnttab, is there a more convenient way?
-Arne
On 08/13/2012 12:22 PM, Robert Buhren wrote:
> Hello,
>
> i wanted to test the new send/receive feature and i can't manage to send
> a snapshot to a file. I always get the error
> "ERROR: could not resolve root_id for".
>
> I'm using kernel 3.6-rc1 and the latest btrfs progs from git.
>
> This is what i'm doing:
>
> mount -o subvolid=0,discard,compress=lzo /dev/sda4 /mnt/ROOT_BTRFS
>
> [root@robert-laptop mnt]# /home/robert/ArchLinux/btrfs-progs/btrfs
> subvolume list ROOT_BTRFS/
> ID 256 top level 5 path btrfs_root <--- my rootfs subvolume
> ID 265 top level 5 path btrfs_root-11082012-0023 <--- a "normal"
> snapshot"
> ID 268 top level 5 path root_send <--- a read only snapshot i try to use
> with send
>
> [root@robert-laptop ~]# cd /mnt/ROOT_BTRFS/
> [root@robert-laptop ROOT_BTRFS]#
> /home/robert/ArchLinux/btrfs-progs/btrfs send root_send > outROOT
> At subvol root_send
> ERROR: could not resolve root_id for /mnt/ROOT_BTRFS/root_send
>
> Am i somehow misunderstanding how the send/receive feature should work?
> My idea is to send the "root_send" snapshot to a file and then replay
> that file later on a backup btrfs partition. Once i've done that i can
> just send incremental differences to the backup partition. Is that how
> "send/receive" is supposed to work?
>
> If you need further information just tell me.
>
> Thanks in advance,
>
> Robert
>
>
> PS: Please respond to my email address as i'm not subscribed to the list.
>
> --
> 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
next prev parent reply other threads:[~2012-08-19 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 10:22 Testing new send/receive: "ERROR: could not resolve root_id for" Robert Buhren
2012-08-19 14:59 ` Arne Jansen [this message]
2012-08-20 11:57 ` [PATCH] Btrfs-progs: replace find_mount_root from send code Jan Schmidt
2012-08-23 8:54 ` Robert Buhren
2012-08-24 13:33 ` David Sterba
2012-08-25 8:24 ` Robert Buhren
2012-08-27 9:16 ` Alex Lyakas
2012-08-27 18:37 ` Robert Buhren
2012-08-28 8:27 ` Alex Lyakas
2012-08-28 17:26 ` Alex Lyakas
2012-09-24 17:18 ` David Sterba
2012-10-03 13:01 ` Alex Lyakas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5030FF4C.8080103@gmx.net \
--to=sensille@gmx.net \
--cc=ablock84@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=robert@robertbuhren.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).