blocks|key|1600271|text|我在写入不能(正确)处理时间的文件系统时遇到过这个问题--我认为是SMB共享或FAT之类的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1600272|您的目标文件系统是什么？|1600273|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I've seen that problem when I'm writing to a filesystem which doesn't (properly) handle times -- I think SMB shares or FAT or something.

What is your target filesystem?

blocks|key|1600308|text|如果/foo/bar在NFS+(或者可能是某个FUSE文件系统)上，那么这可能就是问题所在。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1600309|无论哪种方式，将-O+/+--omit-dir-times添加到命令行都可以避免尝试在目录上设置修改时间。|1600310|entityMap^0|2|8|0|8|2|D|G|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

If <code>/foo/bar</code> is on NFS (or possibly some FUSE filesystem), that might be the problem.

Either way, adding <code>-O</code> / <code>--omit-dir-times</code> to your command line will avoid it trying to set modification times on directories.

blocks|key|1600341|text|这可能是因为您对某些文件没有权限。从管理员帐户尝试"sudo+rsync+-av“，启用根帐户并以根用户身份登录。这应该允许你完全控制你的系统并暴力破解你的rsync！;-)我不确定上面提到的--扩展-属性是否会有帮助，但我也把它放进去了，只是为了更好地衡量。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1600342|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It could be that you don't have privileges to some of the files. From an administrator account, try "sudo rsync -av " Alternately, enable the root account and sign in as root. That should allow you to completely hose your system and brute force your rsync! ;-) I'm not sure if the above mentioned --extended-attributes will help, but I threw it in too, just for good measure.

blocks|key|1600373|text|在我的例子中，问题是“接收器挂载点”安装不正确。它处于只读模式(由于某种额外的原因)。看起来rsync正在复制文件，但事实并非如此。我检查了我的fstab文件，并将挂载选项更改为默认值，重新挂载文件系统并再次执行rsync。那就没问题了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1600374|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The problem in my case was that the "receiver mountpoint" was incorrectly mounted. It was in read-only mode (for some extrange reason).
It looked like rsync was copying the files, but it was not.
I checked my fstab file and changed mount options to default, re-mount file system and execute rsync again. All fine then.

blocks|key|1600403|text|这发生在我的一个类型为xfs+(rw,relatime,seclabel,attr2,inode64,noquota)的分区上，其中的目录属于我们都是其成员的组中的另一个用户。在登录之前已经建立了组成员关系，并且整个目录结构都是组可写的。我手动运行了sudo+chown+-R+otheruser.group+directory和sudo+chmod+-R+g%2Brw+directory来确认这一点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1600404|我仍然不知道为什么它最初不能工作，但通过sudo+chown+-R+myuser.group+directory获得所有权解决了它。也许与SELinux有关？|1600405|entityMap^0|B|1C|3H|13|4L|S|0|K|10|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

This happened to me on a partition of type <code>xfs (rw,relatime,seclabel,attr2,inode64,noquota)</code>, where the directories where owned by another user in a group we were both members of. The group membership was already established before login, and the whole directory structure was group-writeable. I had manually run <code>sudo chown -R otheruser.group directory</code> and <code>sudo chmod -R g+rw directory</code> to confirm this.

I still have no idea why it didn't work originally, but taking ownership with <code>sudo chown -R myuser.group directory</code> fixed it. Perhaps SELinux-related?

blocks|key|1600423|text|如果您对源代码或destination...because中最近未修改的文件运行rsync进程，也可能会弹出此错误，因为它无法设置最近修改的文件的时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1600424|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This error might also pop-up if you run the rsync process for files that are not recently modified in the source or destination...because it cant set the time for the recently modified files.

blocks|key|1600459|text|我也有同样的问题。对我来说，解决方案是删除远程文件，然后让rsync重新创建。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1600460|entityMap^0|T|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had the same problem. For me the solution is to delete the remote file and let <code>rsync</code> create again.

blocks|key|1385676|text|我也遇到了这个问题，我遇到的问题是根文件夹的权限问题，根文件夹包含我试图发送的文件。我不关心根文件夹是否包含在rsync中，我只关心它里面有什么。错误来自我的命令，我需要在命令末尾指定一个额外的/。如果尾部没有斜杠，rsync将尝试设置文件夹时间。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1385677|示例：|1385678|这将尝试在html上设置时间|1385679|rsync+/var/www/html/+ubuntu@xxx.xxx.xxx.xxx:html|code-block|syntax|javascript|1385680|这将不会|1385681|rsync+/var/www/html/+ubuntu@xxx.xxx.xxx.xxx:html/|1385682|entityMap^0|1J|5|2P|1|30|5|0|0|5|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|15|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|17|8|@]|D|@]|E|$M|N]]|$1|S|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|T|$]]

I came across this problem as well and the issue I was having was a permissions issue with the root folder that contained the files I was trying to send over. I don't care about that root folder being included with <code>rsync</code> I just care what's in it. The error was coming from my command where I need to specify an additional <code>/</code> at the end. If you do not have that trailing slash <code>rsync</code> will attempt to set times the folder.
Example:
This will attempt to set times on <code>html</code>
<pre><code>rsync /var/www/html/ ubuntu@xxx.xxx.xxx.xxx:html
</code></pre>
This will not
<pre><code>rsync /var/www/html/ ubuntu@xxx.xxx.xxx.xxx:html/
</code></pre>

I'm getting a confusing error from rsync and the initial things I'm finding from web searches (as well as all the usual chmod'ing) are not solving it:

<pre><code>rsync: failed to set times on "/foo/bar": Operation not permitted (1)
rsync error: some files could not be transferred (code 23) 
 at /SourceCache/rsync/rsync-35.2/rsync/main.c(992) [sender=2.6.9]
</code></pre>

It seems to be working despite that error, but it would be nice to get rid of that.

rsync error: failed to set times on "/foo/bar": Operation not permitted

我从rsync得到了一个令人困惑的错误，我从web搜索(以及所有常见的chmod‘’ing)中发现的最初的东西都不能解决它：rsync: failed to set times on "/foo/bar": Operation not permitted (1)rsync error: some files could...

问rsync错误:无法在“/foo/bar”上设置时间:不允许操作
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问rsync错误:无法在“/foo/bar”上设置时间:不允许操作EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问rsync错误:无法在“/foo/bar”上设置时间:不允许操作
EN