Copydbf fails on decryption of encrypted extent that has been pregrown or restored
When an encrypted extent is pregrown during stone startup, or a backup is restored into an encrypted extent and the extent grows, the unused space is initialized to zeros. If this encrypted extent is then decrypted, these pages of zeros are incorrect identified as garbage; and the copydbf operation that is performing the decryption crashes. In this case, the extents are correct; the error is in copydbf.
Workaround
A backup and restore into a non-encrypted repository can achieve the end result, as a work around, until upgrade to 3.6.2 or later.
Last updated: 9/7/21