From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: dsterba@suse.cz, Harald Glatt <mail@hachre.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Backup Options
Date: Tue, 09 Apr 2013 17:03:30 +0200 [thread overview]
Message-ID: <51642DC2.3070308@giantdisaster.de> (raw)
In-Reply-To: <CAOcd+r3LxyxgbkcT+JgnnLkwLy=V=0Gy6ZzY-dLu30b61X_nmg@mail.gmail.com>
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 <dsterba@suse.cz> 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.
prev parent reply other threads:[~2013-04-09 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 17:37 Backup Options Harald Glatt
2013-04-02 23:29 ` Harald Glatt
2013-04-03 2:23 ` Harald Glatt
2013-04-03 2:33 ` Harald Glatt
2013-04-03 17:23 ` David Sterba
2013-04-09 13:13 ` Alex Lyakas
2013-04-09 15:03 ` Stefan Behrens [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=51642DC2.3070308@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=alex.btrfs@zadarastorage.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mail@hachre.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