jmathai
File `ctime` changed, but not `mtime`
Under what circumstances does elodie modify the file such that the change time of the file changes, but not the modified time? I have a photo library that I've been running elodie against for 2 years now. I just updated the elodie code yesterday and did an import run. After the fact, many of my files now have a modified ctime of the run yesterday, but the mtime is unchanged.
I only ask because the software I use to detect bitrot is throwing errors because the contents of the files have changed, but the modified time has not.
Hi @alex-phillips, we should not be changing the ctime as far as I know. We're only setting the atime and mtime. Here's the source with blame. We're calling os.utime.
That being said, I'm not implying that nothing changed that might be now setting the ctime but as far as I can tell that would be a bug -- but I don't have a clear answer as to why that would be happening.
One quick test is to run an import on the same photo and checking the ctime from a commit > 2 years old vs. now. If you're able to do that then please post the results else I'll try to get to it as well.
