Although a version for Ubuntu 18.04 (Bionic Beaver) is not available, I followed a tutorial and installed it using Debian and Ubuntu 17.10 packages. However, code 22 allways occurs when FreeFileSync tries to lock the sync.ffs_lock file in the Windows remote folder.
When will a specific installation for Ubuntu 18.10 be available in which this error no longer occurs?
Upgrade to Ubuntu 18.04 (Bionic Beaver) causes error 22
- Posts: 2
- Joined: 2 May 2018
- Site Admin
- Posts: 7285
- Joined: 9 Dec 2007
Next version will be compiled for 18.04, but this is unrelated to your error code 22 (EINVAL).
- Posts: 2
- Joined: 2 May 2018
I've been using FreeFileSync in earlier versions of Ubuntu on the same network environment that is now occurring error. In versions 17.10 and 16.04 the error code 22 did not happen and started to occur when I upgraded Ubuntu to 18.04.
- Posts: 2
- Joined: 17 Aug 2018
HiI've been using FreeFileSync in earlier versions of Ubuntu on the same network environment that is now occurring error. In versions 17.10 and 16.04 the error code 22 did not happen and started to occur when I upgraded Ubuntu to 18.04. wribeirojr, 21 May 2018, 13:51
I still have this issue
Ubuntu 18.04 used to synchronise 2 NAS (all copy/move/delete/creation work with Nautilus)
During first step "Compare"
"Waiting while directory is locked" xxxxxxxxxx sync.ffs_lock
On the root directory located on the NAS (source and target) there are many file created :
sync.ffs_lock (size 0 bytes)
del.sync.ffs_lock (size 0 bytes)
del.del.sync.ffs_lock (size 0 bytes)
During second step "Synchronize" (mode : mirror)
"Waiting while directory is locked" xxxxxxxxxx sync.ffs_lock
On source : xxxxx Cannot write file xxxxxx /xxxxxsync.ffs_lockxxxx Error code 22 : invalid argument [open]
On target : xxxxx Cannot write file xxxxxx /xxxxxsync.ffs_lockxxxx Error code 22 : invalid argument [open]
Cannot write file xxxxxx.ffs_tmp Error code 22 : invalid argument [open]
Anyone find a way to solve that ?
Thanks
- Posts: 2
- Joined: 17 Aug 2018
Hi
Solved with specific mount command instead of automatic mount from Nautilus
sudo mount -t cifs -o username=<name on SMB server>,password=<...>,\
gid=1000,uid=1000 \
//<IP of Samba Share>/<share name> ~/Desktop/<SMB folder>
Thanks to Zenju from another post.
Solved with specific mount command instead of automatic mount from Nautilus
sudo mount -t cifs -o username=<name on SMB server>,password=<...>,\
gid=1000,uid=1000 \
//<IP of Samba Share>/<share name> ~/Desktop/<SMB folder>
Thanks to Zenju from another post.