Ned Bass 65dcb0f67a Handle new dnode size in incremental backup stream ... When receiving an incremental backup stream, call dmu_object_reclaim_dnsize() if an object's dnode size differs between the incremental source and target. Otherwise it may appear that a dnode which has shrunk is still occupying slots which are in fact free. This will cause a failure to receive new objects that should occupy the now-free slots. Add a test case to verify that an incremental stream containing objects with changed dnode sizes can be received without error. This test case fails without this change. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Ned Bass <bass6@llnl.gov> Closes #6366 Closes #6576		2017-09-05 16:09:15 -07:00
..
avl	OpenZFS 7028 - avl_destroy_nodes supports emptying, not just destroying, an avl tree	2017-08-30 12:08:38 -07:00
icp	Retire legacy test infrastructure	2017-08-15 17:26:38 -07:00
nvpair	OpenZFS 2976 - remove useless offsetof() macros	2017-08-30 15:53:38 -07:00
unicode	codebase style improvements for OpenZFS 6459 port	2017-01-22 13:25:40 -08:00
zcommon	Native Encryption for ZFS on Linux	2017-08-14 10:36:48 -07:00
zfs	Handle new dnode size in incremental backup stream	2017-09-05 16:09:15 -07:00
.gitignore	Improve gitignore	2017-05-25 10:14:13 -07:00
Makefile.in	Retire legacy test infrastructure	2017-08-15 17:26:38 -07:00