Jitendra Patidar 3ed9d6883b Enforce "-F" flag on resuming recv of full/newfs on existing dataset ... When receiving full/newfs on existing dataset, then it should be done with "-F" flag. Its enforced for initial receive in checks done in zfs_receive_one function of libzfs. Similarly, on resuming full/newfs recv on existing dataset, it should be done with "-F" flag. When dataset doesn't exist, then full/new recv is done on newly created dataset and it's marked INCONSISTENT. But when receiving on existing dataset, recv is first done on %recv and its marked INCONSISTENT. Existing dataset is not marked INCONSISTENT. Resume of full/newfs receive with dataset not INCONSISTENT indicates that its resuming newfs on existing dataset. So, enforce "-F" flag in this case. Also return an error from dmu_recv_resume_begin_check() in zfs kernel, when its resuming full/newfs recv without force. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Chunwei Chen <david.chen@nutanix.com> Signed-off-by: Jitendra Patidar <jitendra.patidar@nutanix.com> Closes #13856 Closes #13857		2022-09-27 16:34:27 -07:00
..
callbacks	autoconf: use include directives instead of recursing down tests (mostly)	2022-05-10 10:20:09 -07:00
cmd	Fix userspace memory leaks found by Clang Static Analzyer	2022-09-26 17:18:05 -07:00
include	ZTS: parameter expansion in zfs_unshare_006_pos	2022-09-15 13:14:35 -07:00
tests	Enforce "-F" flag on resuming recv of full/newfs on existing dataset	2022-09-27 16:34:27 -07:00
.gitignore	autoconf: use include directives instead of recursing down cmd	2022-05-10 10:18:38 -07:00
Makefile.am	autoconf: use include directives instead of recursing down tests (mostly)	2022-05-10 10:20:09 -07:00