When I try to copy from my local attached storage to my SMB mapped storage. I get this error
EINVAL: Invalid argument [fcntl(F_PREALLOCATE)]
What I tried
Resetting my source files and directory with chmod 777
Made sure to strip spaces, apostrophes, question marks, quotes from source filenames
Set the destination directory with chmod 777 from the storage server
What I can do
Using finder, I can copy the folder with all the files into the destination. I can make files from finder in the destination. I'm not sure why FreeFileSync doesn't work and finder does work.
Macos File copy to SMB storage Error EINVAL F_PREALLOCATE
- Posts: 3
- Joined: 18 Feb 2021
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
Fixed! Thanks for your report. https://www.mediafire.com/file/g9e778rlmd56ng6/FreeFileSync_11.7_beta_macOS%25282%2529.zip
- Posts: 3
- Joined: 18 Feb 2021
That looks like it's working now. I will report back if there are any other issues.Fixed! Thanks for your report. https://www.mediafire.com/file/g9e778rlmd56ng6/FreeFileSync_11.7_beta_macOS%25282%2529.zip Zenju, 18 Feb 2021, 09:37
- Posts: 1
- Joined: 18 May 2021
With version 11.10, I'm still (and always have been) getting a variation on this error simply copying from my local Macbook Air to another iMac on our LAN, namely:
"Cannot write file {file path details...}
EIO: Input/output error [fcntl(F_PREALLOCATE)]"
Up until now, I thought perhaps it was because I'm still running High Sierra (10.13.6) on the Air, but having seen that the above turned out to be an application error, I thought I'd finally say something about my variation of it!
"Cannot write file {file path details...}
EIO: Input/output error [fcntl(F_PREALLOCATE)]"
Up until now, I thought perhaps it was because I'm still running High Sierra (10.13.6) on the Air, but having seen that the above turned out to be an application error, I thought I'd finally say something about my variation of it!
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
Thanks for letting me know. I'll have FFS ignore EIO in this case because F_PREALLOCATE is only "nice to have".With version 11.10, I'm still (and always have been) getting a variation on this error simply copying from my local Macbook Air to another iMac on our LAN, namely:
"Cannot write file {file path details...}
EIO: Input/output error [fcntl(F_PREALLOCATE)]"
Up until now, I thought perhaps it was because I'm still running High Sierra (10.13.6) on the Air, but having seen that the above turned out to be an application error, I thought I'd finally say something about my variation of it! Houdini, 18 May 2021, 16:56