You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found more than 60000 files with mtime < 86400 in my instance (SQL count).
solvable_files.sh script is very slow, it has been running for 4 hours in "list mode" and it is not finished, but maybe I can slow it down again :
Why not use "ctime" to correct "mtime" in database?
The last change date is often the same as the last modification date (metadata are rarely changed).
This might avoid losing some data by entering the current date in the ctime.
Am I wrong ?
The text was updated successfully, but these errors were encountered:
I found more than 60000 files with mtime < 86400 in my instance (SQL count).
solvable_files.sh script is very slow, it has been running for 4 hours in "list mode" and it is not finished, but maybe I can slow it down again :
Why not use "ctime" to correct "mtime" in database?
The last change date is often the same as the last modification date (metadata are rarely changed).
This might avoid losing some data by entering the current date in the ctime.
Am I wrong ?
The text was updated successfully, but these errors were encountered: