From: Ian Kelling <iank@fsf.org>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs receive: ERROR: clone: did not find source subvol (user error, not a bug)
Date: Sun, 21 May 2023 18:26:41 -0400 [thread overview]
Message-ID: <87ilclpbaj.fsf@fsf.org> (raw)
In-Reply-To: <87a5ymct4o.fsf@fsf.org>
Scratch that, I had the error again, and there was no simultaneous
snapshots. Again, I needed to wipe the relevant snapshots to get work
done, but next time I'm going to try to save them off for further debugging.
Ian Kelling <iank@fsf.org> writes:
> Upon further investigation, I'm pretty sure there was an error on my
> end, nothing wrong with btrfs. A cronjob was creating a snapshot on the
> wrong host with a name that lead me to think it was from a different
> host. Thank you everyone for the help.
prev parent reply other threads:[~2023-05-21 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 14:02 bug: btrfs receive: ERROR: clone: did not find source subvol Ian Kelling
2023-01-31 16:57 ` Andrei Borzenkov
2023-02-18 14:42 ` Ian Kelling
2023-02-24 17:55 ` Andrei Borzenkov
2023-05-02 21:22 ` btrfs receive: ERROR: clone: did not find source subvol (user error, not a bug) Ian Kelling
2023-05-21 22:26 ` Ian Kelling [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=87ilclpbaj.fsf@fsf.org \
--to=iank@fsf.org \
--cc=arvidjaar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.