SOLVED Rsync errors - mkstemp "<filepath>" (in <poolname>) failed: Operation not permitted

[oRAirwolf]

I am having an issue that is preventing me from backing up my server to another FreeNAS server. Both servers are on 11.2 U4.1 and both have the datasets configured as Windows type shares. I used to get an error saying it could not set permissions, but now after updating (may or may not be related), I am getting the following errors:

May 12 17:01:48 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/.chep_cura_profiles_4_0.zip.iZQu76" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:01:48 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/CHEP_Cura_Profiles/.Magic0.12.curaprofile.ftxhZN" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:01:48 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/CHEP_Cura_Profiles/.Magic0.20.curaprofile.cNOV2W" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:01:48 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/CHEP_Cura_Profiles/.Magic0.28.curaprofile.x8OaVD" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:01:48 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/CHEP_Cura_Profiles/.NinjaFlex.curaprofile.RGSETS" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:01:48 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/__MACOSX/CHEP_Cura_Profiles/._Magic0.12.curaprofile.sJyf7R" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:01:48 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/__MACOSX/CHEP_Cura_Profiles/._Magic0.20.curaprofile.PDZw0z" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:42:08 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/__MACOSX/CHEP_Cura_Profiles/._Magic0.28.curaprofile.Ft8rSF" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:42:08 epsilonshrike rsync: rsync: mkstemp "/3D.Printer/Cura Profiles/chep_cura_profiles_4_0/__MACOSX/CHEP_Cura_Profiles/._NinjaFlex.curaprofile.0CcWTZ" (in RAIDZ1Pool) failed: Operation not permitted (1)
May 12 17:42:33 epsilonshrike rsync: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1191) [sender=3.1.3]

Does anybody know what might be causing this error? I saw that there used to be a bug that was causing this issue with rsync back in 2016, which has since been fixed. It recommended adding

Code:

-A --no-perms

to the rsync arguments. It did not make a difference.

Here is a screenshot of my rsync settings on the server that is initiating the scheduled task:

Here is the configuration for the rsync service on the recipient server:

Here is a screenshot of the user that the rsync service on the recipient server is using:

 

[oRAirwolf]

ttt

 

[KrisBee]

Shouldn't "-no-perms" be written as "--no-perms"?

 

[oRAirwolf]

Shouldn't "-no-perms" be written as "--no-perms"?

It may not show up clearly, but that is how I have it in the screenshot.

 

[KrisBee]

A couple of relevant threads:

https://www.ixsystems.com/community/threads/rsync-directories-written-files-not.27803/

https://www.ixsystems.com/community...rmissions-support-for-windows-datasets.43973/

 

[oRAirwolf]

A couple of relevant threads:

https://www.ixsystems.com/community/threads/rsync-directories-written-files-not.27803/

https://www.ixsystems.com/community...rmissions-support-for-windows-datasets.43973/

I appreciate you providing those links. I am still waiting for verification that the rsync completes, but it looks like this one had the answer: https://www.ixsystems.com/community...rmissions-support-for-windows-datasets.43973/

 

[alveolina]

Hi folks, I know this post is mostly relevant to Windows but I'm having these issues with Linux. I'm using the following:

Code:

sudo rsync -rvHS --progress --stats --whole-file --delete --no-perms /mnt/server1/Backup/ /mnt/server2/

Basically, from Server1 (normal Debain 11 machine) I mounted the NFS share from my Truenas server (server2) on the /mnt/server2/ folder.

Make no difference whether I have the -a or -A in the above (either or both). I don't have NFS4 activated on Truenas. Server 1 is using NFS4. Could this be the problem?

$cat /etc/mtab on Server 1 is showing

Code:

192.168.20.2://mnt/server2/Backup /mnt/server2 nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.
20.2,mountvers=3,mountport=51768,mountproto=udp,local_lock=none,addr=192.168.20.2 0 0

This suggests to me that even though Server 1 is NFS4 client, it has mounted Server 2 share as NFS3. So maybe this is not the problem.

Has anyone encountered this problem with Linux machines?

Code:

rsync: mkstemp "/mnt/server2/Armory-Bitcoin/.bitcoin/blocks/.blk00077.dat.2vfCbf" failed: Operation not permitted (1)