How to make my explorer show the creation date correctly?
Everytime I rename a folder, all the files got modified to the current date, this way my files all have the same modified date/creation date. I can't sort them.
Run the command 'rclone version' and share the full output of the command.
rclone v1.65.0
os/version: Microsoft Windows 10 Pro 22H2 (64 bit)
os/kernel: 10.0.19045.3693 (x86_64)
os/type: windows
os/arch: amd64
go/version: go1.21.4
go/linking: static
go/tags: cmount
Which cloud storage system are you using? (eg Google Drive)
AWS S3
The command you were trying to run (eg rclone copy /tmp remote:tmp)
Paste command here
C:\rclone\rclone.exe mount JMFCloud:jmf-cloud Y:\Cloud --vfs-case-insensitive --vfs-cache-mode full --vfs-write-back 10s --vfs-cache-max-age 300s --vfs-cache-poll-interval 60s --cache-dir %temp% --network-mode --dir-cache-time 5s --use-server-modtime --no-console
Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
Is not quite a problem that is ocurring, I just wanna a way to sort the files by creation or modified. Everytime I rename a folder, all inside files change the creation date to the atual date.
Look the screenshot here:
And as @asdffdsa explained by using --use-server-modtime you are asking rclone to use server modified time instead of object metadata. After this operation all three objects have the same modtime as expected.
So do I have a solution? I need to remove the --use-server-modtime from the command and will fix this? Or this wont work?
Edit:
I test this, removing the --use-server-modtime do the trick, I can see all the files creating date, but folders that have a lot of files, is takes too long to load. Its is not very practical.
without --use-server-modtime, rclone has to make an addtional api call for each and every file.
so keep in mind that, with aws, there is a financial cost to api calls....
"C:\rclone\rclone.exe mount JMFCloud:jmf-cloud Y:\Cloud --vfs-case-insensitive --vfs-cache-mode full --vfs-write-back 10s --vfs-cache-max-age 300s --vfs-cache-poll-interval 60s --cache-dir %temp% --network-mode --dir-cache-time 80000s --use-server-modtime --no-console"
My situation is this, I have a small office, 5 different people access those files and are mounted on their machines, it is synced and fast, if someone change something, automatically changes for everyone. But I don't know if all those parameters are good and essencial for speed and costs.
I see that remove --use-server-modtime will increse the time to load the files and the api call, but will show the original creation time of the files, even if I rename a folder or cut a file.
If you guys could share the best scenarios for my situation, I will appriciate.
only you can decide about that tradeoff.
the more api calls, the more cost.
you can monitor that at aws s3 website.
or choose another s3 provider, that does not charge for api calls, such as wasabi or idrive.
or a provider that supports something that is close to real-time changenotify such as gdrive, onedrive, or dropbox.
that means rclone will not notice changes at aws for 80000s, which is not what you want.
would need to set that to a small value, which would use more api calls.
fwiw, when i setup an small office, i prefer to keep the files local.
and use clould for backups.
About the files locally, I need use the rclone, because here in my country, I need a solution that show the log of the files, who created, who deleted, and stuffs like this. We have a law about this, before that, I use this solution of files locally and cloud backup.
ok, but what is wrong with using the operating system for that?
and how do you plan to handle file locking, prevent multiple users from accessing the same file at the same time, etc...
but if you must use cloud based, nextcloud might work for you.