On Sat, Aug 12, 2017 at 9:40 PM, <siranee.ja@xxxxxxxxx> wrote: > [root@backuplogC7 ~]# rsync -avnc /var/lib/mariadb/mysql_201708090830/ > root@192.168.45.166://var/lib/mariadb/mysql_201708090830/ > sending incremental file list > ./ > ib_logfile1 > ibdata1 > > sent 3779 bytes received 25 bytes 507.20 bytes/sec > total size is 718361496 speedup is 188843.72 (DRY RUN) OK so I don't think this can be a sync related problem. That snapshot has been committed to disk days ago. There's definitely something wrong with the incremental send/receive, but it's unclear whether this is a kernel bug (send side) or btrfs-progs (receive side), or if there's any chance of file system corruption/confusion happening with either of the two subvolumes on the origin or the subvolume (parent) on the destination. So that means you're really in the weeds on what to do next. Try deleting mysql_201708090830/ snapshot on the destination. And resend but this time do a full send of that snapshot, don't use -p. I wonder if a full send, rather than incremental makes a difference. Follow it up with the rsync command to compare origin and destination. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
