linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Hart" <jfhart085@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: ERROR: cannot find parent subvolume, can't see reason for it.
Date: Sat, 29 Apr 2017 23:10:48 -0400	[thread overview]
Message-ID: <590555B8.3070006@gmail.com> (raw)

I am trying to do a "send -p src/snp1 src/snp2 dst/" and getting the 
following error:

ERROR: cannot find parent subvolume

The "src/snp1" is present in both "src/" and "dst/".   The "src/snp2" is 
present in "src/" .
The send works when "-p" is not used, but will not work when it is.

I imagine I am missing something obvious but cannot see what, and would 
appreciate some suggestions on what might be causing the error.

note: I have sent several queries to this list, but have not heard 
anything back.   I hope they have not been inappropriate.  If so, I 
would be grateful if you would let me know, or if there is somewhere 
else I should be going for advice.

I have had pretty good luck with the basics of btrfs and have high hopes 
for it.  I do seem to be having some difficulty getting much beyond 
basic functionality with small flat filesystem layouts, and will soon 
have to revert back to ext4 for some of the more complex functionality I 
made use of under that.   I look forward to seeing what further progress 
might be had with btrfs, and hope to be able to use it in a few years time.


             reply	other threads:[~2017-04-30  3:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30  3:10 J. Hart [this message]
2017-04-30  7:03 ` ERROR: cannot find parent subvolume, can't see reason for it Duncan
2017-04-30 20:43 ` Chris Murphy
2017-04-30 20:57   ` J. Hart
     [not found] <20170430000452.2dcc1591@ws>
2017-04-30 16:56 ` J. Hart

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=590555B8.3070006@gmail.com \
    --to=jfhart085@gmail.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).