aunetx
commented
9 months ago This also consistently happens when the partition that is synced is unmounted (which unfortunately happens sometimes when I log into windows, and go back to fedora):
- the partition is unmounted (because the ntfs partition is faulty)
- I repair the partition (just a matter of resetting a flag, data and metadata do not change)
- I remount the partition (with filen opened or closed, no difference)
- when filen is launched again (or if it is already running), it starts to re-upload my entire 10Gb folder into the cloud: I think it believes the files have changed, but data and metadata were the same before filen was launched
The problem is not so much the upload (because it happens rarely, and it is not so bad), but the real problem is that in the process, filen changes the metadata (and especially the modification timestamp) of the picture on my own drive: this is what causes the pictures to be uploaded again, and ALL my pictures now have arbitrary and unuseful timestamps (which is very annoying to be honest...).
Hello, I am a new subscriber, and I am currently uploading my photo library to the cloud.
It was finishing the upload (maybe 20 files left), and I closed the lid -- like I did several times earlier, without problem. However, after opening the lid, filen restarted the upload, with 200 files left. It looks like something happened, that made the metadata of some lately-uploaded files to be updated on my disk: the 'last modified' date is now 'Today' (eventhough it is actually 2 years ago), and filen is thus re-uploading them (eventhough they are bit-to-bit identical to the last uploaded version).
Is this normal? It does not seem so to me, but at least no important data was lost so that's maybe expected behaviour.
I am using linux (fedora 39), with the appimage version, the filesystem is NTFS (as it is shared with windows -- but this has no influence here).