-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
External Storage - "modified" date bug #16640
Comments
I just noticed same thing, except some say minutes ago, and some say thousands of years in the future LOL This is on a local Ubuntu 18 Nexcloud Version 16 with the external drive being a 2TB Seagate USB hard drive. I have a smaller folder (36GB) of music on same drive that is reading modification times correctly. The folder with bad mod dates that i just added yesterday with screenshot from my "files" area of my NC install is a 72GB folder of digital photos. I added just the "folder" of the hard drive separately in the External Drives connections. So 1 exernal hard drive connection in my NC is "pathToDrive/MUSIC" and the other "pathToDrive/PHOTOS" |
Same here. NextCloud 19.0.2, upgraded from NC 18. This seems to be a regression from 18. The "Modified Date" is shown as the date it was scanned at, and not the actual filesystem modification date now. Has there been a change? |
-- Apologies for double posting, just noticed that this only happens for the folders modified date. The actual files stay with their original date, as expected. @pilsnerbeer @deusoz let me know if your issue is the same, otherwise I'll create a separate one instead of hijacking yours, which may be a different one altogether. |
I can reproduce this on NC21.0.2. |
Any relation to nextcloud/text#3543 ? |
Hi, please update to 24.0.8 or better 25.0.2 and report back if it fixes the issue. Thank you! |
25.0.2 seems fixed. Just scanned old files, it immediately updated the date to the expected date - both files and folders, which was my comment. |
Great! Thanks for verifying! :) |
Steps to reproduce
Expected behaviour
The "modified" data should not be changed if you merely open the storage. - change it only when modifications were done inside that storage.
Actual behaviour
Modification data updates after opening the storage and not really editing anything inside it
The text was updated successfully, but these errors were encountered: