Skip to content
Browse files

Fix incorrect error message for raw receive

This patch fixes an incorrect error message that comes up when
doing a non-forcing, raw, incremental receive into a dataset
that has a newer snapshot than the "from" snapshot. In this
case, the current code prints a confusing message about an IVset
guid mismatch.

This functionality is supported by non-raw receives as an
undocumented feature, but was never supported by the raw receive
code. If this is desired in the future, we can probably figure
out a way to make it work.

Reviewed by: Brian Behlendorf <>
Reviewed by: Matthew Ahrens <>
Signed-off-by: Tom Caputi <>
Issue #8758
Closes #8863
  • Loading branch information...
tcaputi authored and behlendorf committed Jun 10, 2019
1 parent ba505f9 commit 581c77e725b3bff3f9539dd06b7ea83d92161abc
Showing with 9 additions and 2 deletions.
  1. +9 −2 module/zfs/dmu_recv.c
@@ -158,9 +158,16 @@ recv_begin_check_existing_impl(dmu_recv_begin_arg_t *drba, dsl_dataset_t *ds,
} else {
* If we are not forcing, there must be no
* changes since fromsnap.
* changes since fromsnap. Raw sends have an
* additional constraint that requires that
* no "noop" snapshots exist between fromsnap
* and tosnap for the IVset checking code to
* work properly.
if (dsl_dataset_modified_since_snap(ds, snap)) {
if (dsl_dataset_modified_since_snap(ds, snap) ||
(raw &&
dsl_dataset_phys(ds)->ds_prev_snap_obj !=
snap->ds_object)) {
dsl_dataset_rele(snap, FTAG);

0 comments on commit 581c77e

Please sign in to comment.
You can’t perform that action at this time.