mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2026-05-24 03:08:51 +03:00
Fix handling of maxblkid for raw sends
Currently, the receive code can create an unreadable dataset from a correct raw send stream. This is because it is currently impossible to set maxblkid to a lower value without freeing the associated object. This means truncating files on the send side to a non-0 size could result in corruption. This patch solves this issue by adding a new 'force' flag to dnode_new_blkid() which will allow the raw receive code to force the DMU to accept the provided maxblkid even if it is a lower value than the existing one. For testing purposes the send_encrypted_files.ksh test has been extended to include a variety of truncated files and multiple snapshots. It also now leverages the xattrtest command to help ensure raw receives correctly handle xattrs. Reviewed-by: Paul Dagnelie <pcd@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Matt Ahrens <mahrens@delphix.com> Signed-off-by: Tom Caputi <tcaputi@datto.com> Closes #8168 Closes #8487
This commit is contained in:
committed by
Brian Behlendorf
parent
146bdc414c
commit
369aa501d1
+2
-1
@@ -477,7 +477,8 @@ int dmu_object_set_blocksize(objset_t *os, uint64_t object, uint64_t size,
|
||||
|
||||
/*
|
||||
* Manually set the maxblkid on a dnode. This will adjust nlevels accordingly
|
||||
* to accommodate the change.
|
||||
* to accommodate the change. When calling this function, the caller must
|
||||
* ensure that the object's nlevels can sufficiently support the new maxblkid.
|
||||
*/
|
||||
int dmu_object_set_maxblkid(objset_t *os, uint64_t object, uint64_t maxblkid,
|
||||
dmu_tx_t *tx);
|
||||
|
||||
Reference in New Issue
Block a user