linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rory Campbell-Lange <rory@campbell-lange.net>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: Arne Jansen <sensille@gmx.net>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs receive to subdirectory
Date: Wed, 10 Oct 2012 23:11:07 +0100	[thread overview]
Message-ID: <20121010221107.GA19266@campbell-lange.net> (raw)
In-Reply-To: <CAOcd+r2DwTz_F3VHLRiQ7+fafqLrSTvib=P38hHYqYCY-5gGkA@mail.gmail.com>

On 09/10/12, Alex Lyakas (alex.btrfs@zadarastorage.com) wrote:
> Hi Rory, Arne,
> I think the problem is that currently mnt_fd in struct btrfs_receive
> is used both as "mount root" and "directory in which the
> subvolume/snapshot needs to be created".
> Arne, does the following patch make sense? It uses Jan's
> find_mount_root function. With this patch both Rory's tests seem to
> work for me.

Hi Alex

I haven't had a chance to test this. I'm also on 89fe5b5f of progs
recommended to my by Chris for send/receive testing and your patch
doesn't apply for me. Are you using another revision?

Regards
Rory

-- 
Rory Campbell-Lange
rory@campbell-lange.net

  reply	other threads:[~2012-10-10 22:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 16:30 btrfs receive to subdirectory Rory Campbell-Lange
2012-10-08 20:53 ` Arne Jansen
2012-10-09 11:18   ` Rory Campbell-Lange
2012-10-09 13:25     ` Alex Lyakas
2012-10-10 22:11       ` Rory Campbell-Lange [this message]
2012-10-11  9:10         ` Alex Lyakas
2012-10-11 11:33           ` Rory Campbell-Lange
2012-10-11 12:51             ` Alex Lyakas
2012-10-11 14:56               ` Rory Campbell-Lange
2012-10-11 18:38                 ` Alex Lyakas
2012-10-12 11:26                 ` Alex Lyakas
2012-10-12 16:10                   ` Rory Campbell-Lange
2012-10-13 17:00                     ` 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=20121010221107.GA19266@campbell-lange.net \
    --to=rory@campbell-lange.net \
    --cc=alex.btrfs@zadarastorage.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sensille@gmx.net \
    /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).