When attempting to delete a default ACL an error return of ENODATA means there
wasn't a default ACL in the first place. Don't treat this as an error as it
means we're now where we wanted to be, i.e. without a default ACL.
Created attachment 6247 [details]
Patch to fix deleting non-existent default ACL
How can the situation arise? If it arises only by a concurrent modification to the destination, I don't care much. There are lots of ways rsync can mess up with concurrent modifications to the destination.
I was seeing the error on an rsync -A into a fresh destination, where the destination directory itself doesn't have a default ACL.
...doh! As it turns out, the error was because my destination filesystem didn't have ACLs enabled. Sorry for the noise!