Filipe,
I realize its another bug. Two additional pieces of info that might help.
One, btrfs-progs was at 4.1.2 (I missed a tag= in my git pull). Second
is that I have been able to recreate this issue three times over a period
of
two to three days (tring again with 4.2.3). My fs is probably a good
testcase for any patches that appear.
Meanwhile I've been falling back to rsync which always works but is so much
slower.
TIA
Ed
On Sunday, October 25, 2015 9:42:54 AM EDT, Filipe Manana wrote:
On Sun, Oct 25, 2015 at 1:38 PM, Ed Tomlinson <e...@aei.ca> wrote:
Filipe,
Its still not perfect. Here I can do sequential sends a few times then I
get something like this:
[root@grover snap]# sh -x brh
+ base=/snap/shot ...
Different and unrelated problem.
Yes, we know there are still some problems regarding send issuing
invalid/outdated paths to the send stream. Nothing to do with
incorrect uuids in the send stream.
Please let me know if there is anything you would like me to try. I am
running 4.2 with the 4.3 for-linus tree applied and the 4.2.x patches with
btrfs fixes removed. On top of this are a few patches from this list.
TIA
Ed Tomlinson ...
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
