Syncovery v9.38 for DSM7 - Error setting timestamp

English Support for Syncovery on Linux etc.
Post Reply
gabiru
Posts: 3
Joined: Tue Jul 06, 2021 5:36 pm

Syncovery v9.38 for DSM7 - Error setting timestamp

Post by gabiru »

I've been going on circles trying to fix an error that occurs when the backup tries to set the timestamp.

The files are copied fine but because the timestamp is not the same as in the original files (it's the backup time), the next time the backup runs it copies all the files again.

The error only shows in the log files (see example below). I've set the folder permissions so that syncovery can read/write. Ignoring the timestamp solves this but is far from ideal.

fpchown(/volumeUSB2/usbshare/test/spot this 10.txt,1026,100)=-1, errno=1
Error setting timestamp for /volumeUSB2/usbshare/test/spot this 10.txt errno=1


Does anyone have any ideas how to fix this? Thanks in advance.

tobias
Posts: 715
Joined: Tue Mar 31, 2020 7:37 pm

Re: Syncovery v9.38 for DSM7 - Error setting timestamp

Post by tobias »

Hello,
I don't have specific info on USB drives, but you may need to install Syncovery to run as root with the new "Syncovery Linux Installer Utility for Windows", which you can download from
https://www.syncovery.com/download/linux/

gabiru
Posts: 3
Joined: Tue Jul 06, 2021 5:36 pm

Re: Syncovery v9.38 for DSM7 - Error setting timestamp

Post by gabiru »

Hi Tobias. And on that note did another test and when backed up to the internal drive the error does not occur. Also noticed that the USB drive is formatted in NTFS which may not help. Will run some more tests. Thanks

tobias
Posts: 715
Joined: Tue Mar 31, 2020 7:37 pm

Re: Syncovery v9.38 for DSM7 - Error setting timestamp

Post by tobias »

Hi,
maybe it's a bug in the NTFS implementation in DSM7. I will try it here also.

FYI, error 1 means Permission Denied.

gabiru
Posts: 3
Joined: Tue Jul 06, 2021 5:36 pm

Re: Syncovery v9.38 for DSM7 - Error setting timestamp [Solved]

Post by gabiru »

Thanks Tobias. formatting the external usb drive into ext4 seems to have solved the problem. Everything seems to run smoothly now. Cheers.

Post Reply