search

kahing / goofys

a high-performance, POSIX-ish Amazon S3 file system written in Go
Apache License 2.0
5.2k stars 522 forks source link

Update mtime of moved files to improve consistency with S3 #399

Open tbastos opened 5 years ago

tbastos commented 5 years ago

When a file is moved, its mtime remains unchanged locally (with caching enabled) even though it changes remotely in S3, which creates inconsistencies until the filesystem is re-mounted.

In the spirit of making things more predictable (less error-prone), could goofys perhaps update the local mtime of moved files to stay consistent with remote S3 timestamps?

kahing commented 5 years ago

Great idea, although not sure if it's possible due to kernel inode cache? Do you want to give this a try?