In short:
Thank you so much. The pi date (2021.03.14) version of 2.0 fixed this problem.
viewtopic.php?f=20&t=3478#p10876Details:
I got the following errors when sending snapshots of some file systems. I guess it might be problems caused by previous failures. The problem resolved after I destroyed the last snapshot on target file system.
Batch 1 -
- Code: Select all
+ zfs send -I earth/Docks@2021-02-28-204659-Sync earth/Docks@2021-03-18-230025-Sync
+ zfs receive -F W/Backups/earth/Docks
cannot receive incremental stream: most recent snapshot of W/Backups/earth/Docks does not
match incremental source
warning: cannot send 'earth/Docks@2021-03-07-184706-Sync': signal received
warning: cannot send 'earth/Docks@2021-03-18-230020-Sync': Broken pipe
warning: cannot send 'earth/Docks@2021-03-18-230025-Sync': Broken pipe
Batch 2 -
Some of file systems will have the following errors when sending snapshots. However, it does not have the same problem after second try (without doing anything).
- Code: Select all
+ zfs send -I earth/Life/Dots@2021-02-28-204712-Sync earth/Life/Dots@2021-03-18-230028-Sync
+ zfs receive -F W/Backups/earth/Life/Dots
cannot receive incremental stream: checksum mismatch
+ zfs send -I earth/Life/Pal@2021-02-28-204712-Sync earth/Life/Pal@2021-03-18-230029-Sync
+ zfs receive -F W/Backups/earth/Life/Pal
cannot receive incremental stream: invalid backup stream
References -
Sending and Receiving ZFS Data - Oracle Solaris ZFS Administration Guide
https://docs.oracle.com/cd/E26505_01/ht ... gbchx.htmlDisabling access time (atime) updates on ZFS file systems -- Prefetch Technologies
https://prefetch.net/blog/2006/07/25/di ... le-system/ZFS Best Practices and Caveats | Bigstep Blog
https://bigstep.com/blog/zfs-best-practices-and-caveats