From: Robert White <rwhite@pobox.com>
To: linux-btrfs@vger.kernel.org
Subject: BUG: Replacing a directory with a subvolume breaks incremental snapshots
Date: Fri, 23 May 2014 19:24:09 -0700 [thread overview]
Message-ID: <538002C9.8080503@pobox.com> (raw)
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
next reply other threads:[~2014-05-24 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 2:24 Robert White [this message]
2014-05-25 2:01 ` BUG: Replacing a directory with a subvolume breaks incremental snapshots Filipe David Manana
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=538002C9.8080503@pobox.com \
--to=rwhite@pobox.com \
--cc=linux-btrfs@vger.kernel.org \
/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).