[ZFS] Potential silent data corruption when receiving incremental stream with block size change on receiving side

[Eric Borisch]

That sounds like a potential hole birth issue.

You might consider upgrading to at least 10.4 or 11.1 and re-trying the
send; these added the vfs.zfs.send_holes_without_birth_time (default
true/1) tunable to avoid "numerous hole_birth bugs". See this [1] commit.

  - Eric

[1]
https://svnweb.freebsd.org/base/releng/10.4/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_traverse.c?revision=308086&view=markup

On Tue, Oct 1, 2019 at 5:51 PM Shiva Bhanujan <Shiva.Bhanujan at quorum.com>
wrote:

> Hello,
>
> This seems to be an older email, but I seem to be hitting this in FreeBSD
> 10.3.  Following is the precise version -
>
> FreeBSD R530-Filer-20-194.quorum.net 10.3-RELEASE-p29 FreeBSD
> 10.3-RELEASE-p29 #12 r335461M: Wed Jun 20 16:11:04 PDT 2018
>  root at R520-31-232.quorum.net:/usr/obj/usr/src/sys/QUORUM  amd64
>
> When I send an incremental snapshot, the md5sum of a couple of the files
> in the source and the destination don't match.  The previous incrementals
> don't have a mismatch.
>
> Can somebody please advise on what I should be looking for?  I've checked
> the URLs mentioned here.  The addition or removal of the -L option doesn't
> have any change.
>
> Regards,
> Shiva
>
>
> ________________________________
> From: owner-freebsd-fs at freebsd.org [owner-freebsd-fs at freebsd.org] on
> behalf of Fabian Keil [freebsd-listen at fabiankeil.de]
> Sent: Monday, August 07, 2017 8:10 AM
> To: freebsd-fs at freebsd.org
> Subject: [ZFS] Potential silent data corruption when receiving incremental
> stream with block size change on receiving side
>
> The original message is attached because it is signed.
> ________________________________
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
>