rsync response error when upgrade from 3.3.6 to 3.5.3 about pika

[epubreader]

docker service create \ --name pika-slave \ --publish 9223:9221 \ --mount type=bind,source=/opt/pika/conf/pika.slave.conf,target=/pika/conf/pika.conf \ --mount type=bind,source=/opt/pika/db,target=/pika/db \ --mount type=bind,source=/opt/pika/dump,target=/pika/dump \ --mount type=bind,source=/opt/pika/log,target=/pika/log \ --mount type=bind,source=/opt/pika/dbsync,target=/pika/dbsync \ --network back \ --constraint 'node.labels.name==mongodb2' \ --mode global \ --restart-condition on-failure \ --with-registry-auth \ pikadb/pika:3.5.3 \

我用的是docker swarm， 然后新增slave节点时， 会全量同步， 把dbsync重命名为db 这一步， 会报错，之前的版本是没有问题的
--mount type=bind,source=/opt/epub/pika/log,target=/pika/log
--mount type=bind,source=/opt/epub/pika/dbsync,target=/pika/dbsync \

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

docker service create \ --name pika-slave \ --publish 9223:9221 \ --mount type=bind,source=/opt/epub/pika/conf/pika.slave.conf,target=/pika/conf/pika.conf \ --mount type=bind,source=/opt/epub/pika/db,target=/pika/db \ --mount type=bind,source=/opt/epub/pika/dump,target=/pika/dump \ --mount type=bind,source=/opt/epub/pika/log,target=/pika/log \ --mount type=bind,source=/opt/epub/pika/dbsync,target=/pika/dbsync \ --network back \ --constraint 'node.labels.name==mongodb2' \ --mode global \ --restart-condition on-failure \ --with-registry-auth \ pikadb/pika:3.5.3 \

I use docker swarm, and then when adding a slave node, it will be fully synchronized. When renaming dbsync to db, an error will be reported. There was no problem with the previous version.
--mount type=bind,source=/opt/epub/pika/log,target=/pika/log
--mount type=bind,source=/opt/epub/pika/dbsync,target=/pika/dbsync \

[cheniujh]

补充一个误删除的内容：

[cheniujh]

Bot detected the issue body's language is not English, translate it automatically.

docker service create \ --name pika-slave \ --publish 9223:9221 \ --mount type=bind,source=/opt/epub/pika/conf/pika.slave.conf,target=/pika/conf/pika.conf \ --mount type=bind,source=/opt/epub/pika/db,target=/pika/db \ --mount type=bind,source=/opt/epub/pika/dump,target=/pika/dump \ --mount type=bind,source=/opt/epub/pika/log,target=/pika/log \ --mount type=bind,source=/opt/epub/pika/dbsync,target=/pika/dbsync \ --network back \ --constraint 'node.labels.name==mongodb2' \ --mode global \ --restart-condition on-failure \ --with-registry-auth \ pikadb/pika:3.5.3 \

I use docker swarm, and then when adding a slave node, it will be fully synchronized. When renaming dbsync to db, an error will be reported. There was no problem with the previous version. --mount type=bind,source=/opt/epub/pika/log,target=/pika/log --mount type=bind,source=/opt/epub/pika/dbsync,target=/pika/dbsync \

这里将pika的各个主要目录都做了mount，挂载到了不同的文件系统，这样会带来很多麻烦，一个是你的case:不能跨越文件系统rename导致全量同步失败，二是做bgsave生成dump时，原来是同一个文件系统生成硬链接即可，这样跨越文件系统会实际发生copy。