On Tue, 9 Apr 2013 16:13:22 +0300, Alex Lyakas wrote: > Hi David, > maybe my old patch > http://www.spinics.net/lists/linux-btrfs/msg19739.html > can help this issue? >
The utimensat() call in process_utimes() needs the AT_FDCWD parameter to be able to receive to relative directories. I'm currently assembling a set of btrfs send/receive btrfs-progs related fixes (including the "[PATCH] btrfs-progs: Fix the receive code pathing" from you). A patch for AT_FDCWC is also included. > On Wed, Apr 3, 2013 at 8:23 PM, David Sterba <[email protected]> wrote: >> On Wed, Apr 03, 2013 at 04:33:22AM +0200, Harald Glatt wrote: >>> However what I actually did was: >>> # cd /mnt/restore >>> # nc -l -p 4444 | btrfs receive . >>> >>> After noticing this difference I had to try it again as described in >>> my mail and - oh wonder - it works now!! Giving 'btrfs receive' a dot >>> as a parameter seems to fail in this case. Is this expected behavior >>> or a bug? >> >> Bug. Relative paths do not work on the receive side. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
