許久沒(méi)有管這個(gè)事情……自問(wèn)自答了……
翻了一下評(píng)論曰實(shí)際上是一個(gè)fat文件系統(tǒng)權(quán)限的問(wèn)題……說(shuō)是說(shuō)不能叫做bug……但是總之就當(dāng)個(gè)注意點(diǎn)吧……
參考ben at indietorrent dot org 的回答……
也就是復(fù)制到fat格式的文件系統(tǒng)上時(shí)會(huì)產(chǎn)生如此的錯(cuò)誤……

From the Changelog notes:

"Warnings may be generated if the destination filesystem doesn't permit chown() or chmod() system calls to be made on files — for example, if the destination filesystem is a FAT filesystem."

More explicitly, rename() may still return (bool) true, despite the warnings that result from the underlying calls to chown() or chmod(). This behavior can be misleading absent a deeper understanding of the underlying mechanics. To rename across filesystems, PHP "fakes it" by calling copy(), unlink(), chown(), and chmod() (not necessarily in that order). See PHP bug #50676 for more information.

On UNIX-like operating systems, filesystems may be mounted with an explicit uid and/or gid (for example, with mount options "uid=someuser,gid=somegroup"). Attempting to call rename() with such a destination filesystem will cause an "Operation not permitted" warning, even though the file is indeed renamed and rename() returns (bool) true.

This is not a bug. Either handle the warning as is appropriate to your use-case, or call copy() and then unlink(), which will avoid the doomed calls to chown() and chmod(), thereby eliminating the warning.