On Friday, October 9, 2015 4:24:10 PM EDT, Filipe Manana wrote:
On Wed, Sep 30, 2015 at 8:23 PM, Robin Ruede <r.ruede@xxxxxxxxx> wrote:
This fixes a regression introduced by 37b8d27d between v4.1 and v4.2.
When a snapshot is received, its received_uuid is set to the original
uuid of the subvolume. When that snapshot is then resent to a third
filesystem, it's received_uuid is set to the second uuid
instead of the original one. The same was true for the parent_uuid. ...
Reviewed-by: Filipe Manana <fdmanana@xxxxxxxx>
Thanks for fixing this.
I've added this to my integration branch [1] and will send soon a pull
request to Chris for 4.4, including this fix plus a few others for
send/receive, after some more testing.
I've also made an xfstest for it [1, 2]
Another thanks for this fix. It fixes things here. I am runing 4.2.3 with
the 4.3 btrfs tree pulled on top of it along with this fix. Incremental
sends
are now working again.
Tested-by: Ed Tomlinson <edt@xxxxxx>
This fixes a regression, can we please get into 4.3?
Thanks
Ed Tomlinson
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
