From: Filipe David Manana <fdmanana@gmail.com>
To: Robert White <rwhite@pobox.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: BUG: Replacing a directory with a subvolume breaks incremental snapshots
Date: Sun, 25 May 2014 03:01:00 +0100 [thread overview]
Message-ID: <CAL3q7H7kq73rXdDCdbTVig9WFMXxpWVra24B4DsGJbS2aQc_0g@mail.gmail.com> (raw)
In-Reply-To: <538002C9.8080503@pobox.com>
On Sat, May 24, 2014 at 3:24 AM, Robert White <rwhite@pobox.com> wrote:
> Howdy,
>
> If you remove an existing directory and then create a subvolume with the
> same name the incremental send (btrfs send -p) will die with errno==2 (file
> not found).
>
> Steps to Reproduce:
>
> btrfs subvol create scratch # make a playground
> mkdir scratch/example
> btrfs subvol snap -r scratch scratch_BEFORE
> rmdir scratch/example
> btrfs subvol create scratch/example
> btrfs subvol snap -r scratch scratch_AFTER
> btrfs send -p scratch_BEFORE scratch_AFTER >/dev/null
>
> The output produced:
> At subvol scratch_AFTER
> ERROR: send ioctl failed with -2: No such file or directory
Fixed here: https://patchwork.kernel.org/patch/4238131/
Thanks Robert.
>
> --
> 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
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
prev parent reply other threads:[~2014-05-25 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 2:24 BUG: Replacing a directory with a subvolume breaks incremental snapshots Robert White
2014-05-25 2:01 ` Filipe David Manana [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=CAL3q7H7kq73rXdDCdbTVig9WFMXxpWVra24B4DsGJbS2aQc_0g@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwhite@pobox.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).