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
After you change a file's modification time (for example using touch) a later stat doesn't reflect this change—the ctime/mtime value seems to be cached. Actually modifiying the file does work as I expect. Here's an example:
$ gdfs -d .cache/gdfs /tmp/gdfs/
$ cd /tmp/gdfs
$ rm test
rm: cannot remove 'test': No such file or directory
Only the access time has changed. However in the Google Drive website the file appears correctly as 'Modified 1 Jan by me'. And after remounting the times are correct:
$ cd ..; fusermount -u /tmp/gdfs; gdfs -d .cache/gdfs /tmp/gdfs/; cd /tmp/gdfs
After you change a file's modification time (for example using
touch
) a laterstat
doesn't reflect this change—the ctime/mtime value seems to be cached. Actually modifiying the file does work as I expect. Here's an example:Now let's make a file called 'test':
So far so good. Now let's change it and pretend it's 2014/Jan/01 at 00:00:
Only the access time has changed. However in the Google Drive website the file appears correctly as 'Modified 1 Jan by me'. And after remounting the times are correct:
touch
ing the time again yields the same result. An actual modification to the file works as expected without remounting:The text was updated successfully, but these errors were encountered: