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 Bye, David Arendt -- 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
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 directoryA 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 -- 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
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-- 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