Re: Troubles with rsync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/10/2018 09:53 PM, Samuel Sieb wrote:
On 06/08/2018 08:48 PM, Robert McBroom via users wrote:
On 06/08/2018 10:57 PM, Robert McBroom wrote:
System is mounted with CIFS with write permission.  NAS only uses version 1.0.

Sample effects
rsync . -av /mnt/external/f27/Packages

rsync: mkstemp "/mnt/external/f27/Packages/.ffmpeg-libs-3.3.6-1.fc27.x86_64.rpm.eZUrRd" failed: Permission denied (13)

It's likely that you can't create files that start with . on CIFS or NTFS.  Try using the "--inplace" option with rsync.
No problem with . filenames in general just in this instance the transmission of the files is inhibited.  Apparently something is happening with the temporary file creation. Using "--inplace" does the copy as desired.  There is the message about the permissions which are apparently inherited from the directory.

rsync: failed to set permissions on "/mnt/external/test/autocorr-en-5.4.7.2-2.fc27.noarch.rpm": Permission denied (13) rsync: failed to set permissions on "/mnt/external/test/cryptsetup-1.7.5-4.fc27.x86_64.rpm": Permission denied (13) rsync: failed to set permissions on "/mnt/external/test/cryptsetup-libs-1.7.5-4.fc27.x86_64.rpm": Permission denied (13)

Using cpio command, files are transfered with a message about the mode change failure.

find . -print |cpio -p -d -m /mnt/external/f27/Packages

cpio: /mnt/external/f27/Packages/./ffmpeg-libs-3.3.6-1.fc27.x86_64.rpm: Cannot change mode to rw-r--r--: Permission denied

NTFS permissions are also different and don't match the Unix permission settings.  You will get the same errors from rsync as well.

The chmod command has no effect on the permission settings of the ntfs files.

There are probably some combinations that would work like removing write from the user or all, but in most cases the permission set isn't possible to represent on NTFS.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/3LVBRFF7F7JIRFZ2BKAMDETXDYBBECPQ/

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/LFBUK7G3ALJRKQGS6M4A444QMKPV3E3D/



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux