Search found 11 matches
- 16 May 2021, 18:52
- Forum: General Discussion
- Topic: cloning issue / 3 installs donation edition
- Replies: 4
- Views: 3748
Re: cloning issue / 3 installs donation edition
Done! Thanks!
- 16 May 2021, 17:15
- Forum: General Discussion
- Topic: cloning issue / 3 installs donation edition
- Replies: 4
- Views: 3748
Re: cloning issue / 3 installs donation edition
OK... but where is "my donation page"? Thanks.
- 16 May 2021, 16:59
- Forum: General Discussion
- Topic: cloning issue / 3 installs donation edition
- Replies: 4
- Views: 3748
cloning issue / 3 installs donation edition
Hi,
I have cloned my SSD to an nvme drive, and when I launched FreeFileSync it say the software has been installed on 3 PC, but in fact it has not... one install has just moved to another disk... anyway to solve that?
Thanks,
Rv
I have cloned my SSD to an nvme drive, and when I launched FreeFileSync it say the software has been installed on 3 PC, but in fact it has not... one install has just moved to another disk... anyway to solve that?
Thanks,
Rv
- 11 Dec 2018, 12:12
- Forum: Help
- Topic: Problem with lock file: Error Code 22: Invalid argument [open]
- Replies: 1
- Views: 1328
Problem with lock file: Error Code 22: Invalid argument [open]
Hi,
I got the following message when trying to copy file on a NAS using smb share on Ubuntu 18.04LTS
"/run/user/1000/gvfs/smb-share:server=130.88.18.205,share=backup_imaging_data_herve_boutin/Inveon_scans"
Cannot write file "/run/user/1000/gvfs/smb-share:server=130.88.18.205,share=backup_imaging ...
I got the following message when trying to copy file on a NAS using smb share on Ubuntu 18.04LTS
"/run/user/1000/gvfs/smb-share:server=130.88.18.205,share=backup_imaging_data_herve_boutin/Inveon_scans"
Cannot write file "/run/user/1000/gvfs/smb-share:server=130.88.18.205,share=backup_imaging ...
- 27 Sep 2018, 09:52
- Forum: General Discussion
- Topic: version 10.4 long initializing and .lock files
- Replies: 9
- Views: 1769
Re: version 10.4 long initializing and .lock files
I know but if I do not exclude them I got an error message saying that FFS cannot delete those .tmp files because they are open. It only happens in Ubuntu and with NAS shares!
- 26 Sep 2018, 15:21
- Forum: General Discussion
- Topic: version 10.4 long initializing and .lock files
- Replies: 9
- Views: 1769
Re: version 10.4 long initializing and .lock files
My mistake: the destination of deleted files was set to "recycle bin", changing this to "delete permanently" in FFS and excluding all tmp file with the filter *ffs.tmp allowed the synchronisation to take place. NB: I have only tried with the NAS share mounted manually through terminal using nfs and ...
- 26 Sep 2018, 14:06
- Forum: General Discussion
- Topic: version 10.4 long initializing and .lock files
- Replies: 9
- Views: 1769
Re: version 10.4 long initializing and .lock files
This is strange as SMB mounting works fine in Nautilus, I can create/delete/modify files in the shares without any issues, it is only FFS that has a problem accessing the shares and writing to them.
I'll try to mount that share manually in terminal and get back to you after testing.
I'll try to mount that share manually in terminal and get back to you after testing.
- 26 Sep 2018, 11:38
- Forum: General Discussion
- Topic: version 10.4 long initializing and .lock files
- Replies: 9
- Views: 1769
Re: version 10.4 long initializing and .lock files
Have now rebooted both the PC and NAS and I now get the following message:
Cannot set directory locks for the following folders:
"/run/user/1000/gvfs/smb-share:server=IP.IP.IP.IP,share=share/"
Cannot write file "/run/user/1000/gvfs/smb-share:server=IP.IP.IP.IP,share=share/Del.Del.sync.ffs_lock ...
Cannot set directory locks for the following folders:
"/run/user/1000/gvfs/smb-share:server=IP.IP.IP.IP,share=share/"
Cannot write file "/run/user/1000/gvfs/smb-share:server=IP.IP.IP.IP,share=share/Del.Del.sync.ffs_lock ...
- 26 Sep 2018, 11:25
- Forum: General Discussion
- Topic: version 10.4 long initializing and .lock files
- Replies: 9
- Views: 1769
Re: version 10.4 long initializing and .lock files
Update: this is only happening when working with NAS shares.
- 26 Sep 2018, 11:02
- Forum: General Discussion
- Topic: version 10.4 long initializing and .lock files
- Replies: 9
- Views: 1769
Re: version 10.4 long initializing and .lock files
So the error I get is:
Cannot write file "/run/user/1000/gvfs/smb-share:server=IP.IP.IP.IP,share=file_name_here.ffs_tmp".
Error Code 22: Invalid argument [open]
The file is not open in any applications but Freefilesync!
Cannot write file "/run/user/1000/gvfs/smb-share:server=IP.IP.IP.IP,share=file_name_here.ffs_tmp".
Error Code 22: Invalid argument [open]
The file is not open in any applications but Freefilesync!
- 26 Sep 2018, 10:56
- Forum: General Discussion
- Topic: version 10.4 long initializing and .lock files
- Replies: 9
- Views: 1769
version 10.4 long initializing and .lock files
Hi,
I am using Freefilesync on Ubuntu 18.04 to synchronize folders between an external USB3 HDD and NAS shares (mounted as CIFS in Ubuntu). Since version 10.4 the synchronisation fails, it takes a very long time initializing (scanning for locked folders), creates lots of .lock files (many starting ...
I am using Freefilesync on Ubuntu 18.04 to synchronize folders between an external USB3 HDD and NAS shares (mounted as CIFS in Ubuntu). Since version 10.4 the synchronisation fails, it takes a very long time initializing (scanning for locked folders), creates lots of .lock files (many starting ...