linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Arendt <admin@prnet.org>
To: Marios Titas <redneb8888@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send/receive symlink bug
Date: Thu, 15 Nov 2012 06:59:07 +0100	[thread overview]
Message-ID: <50A484AB.5050600@prnet.org> (raw)
In-Reply-To: <CAAdM644U3k=0N4RsxTont7rObi9zD2FqZZk6X4+M5AtupdtoFA@mail.gmail.com>

Hi,

thanks,

this patch fixes the problem

Bye,
David Arendt

On 11/15/12 05:21, Marios Titas wrote:
> On Wed, Nov 14, 2012 at 5:34 PM, David Arendt <admin@prnet.org> wrote:
>> Hi,
>>
>> I am using kernel 3.7.0-rc5 and latest btrfs-progs git.
>>
>> I am trying btrfs send/receive. When I have a filesystem containing a
>> symlink pointing to a nonexistent destination or a destination created
>> after the symlink was created, btrfs receive aborts with: ERROR: chown
>> link1.txt failed. No such file or directory.
>>
>> Steps to reproduce (/dev/loop0 and /dev/loop1 are test images):
>>
>> mkfs.btrfs /dev/loop0
>> mount /dev/loop0 /u00
>> btrfs subvolume create /u00/test
>> cd /u00/test
>> ln -s test1.txt link1.txt
>> btrfs subvolume snapshot -r /u00/test /u00/test.snapshot
>> mkfs.btrfs /dev/loop1
>> mount /dev/loop1 /u01
>> btrfs send /u00/test.snapshot | btrfs receive /u01
>> ERROR: chown link1.txt failed. No such file or directory
>
> A patch [1] for btrfs-progs that solves this issue was posted a month
> ago but has landed yet on the btrfs-progs git repository.
>
> [1] http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg19539.html


      reply	other threads:[~2012-11-15  5:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 22:34 btrfs send/receive symlink bug David Arendt
2012-11-15  4:21 ` Marios Titas
2012-11-15  5:59   ` David Arendt [this message]

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=50A484AB.5050600@prnet.org \
    --to=admin@prnet.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=redneb8888@gmail.com \
    /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).