Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle common file timestamps #8944

Open
mmmarcos opened this issue Nov 15, 2024 · 1 comment
Open

Handle common file timestamps #8944

mmmarcos opened this issue Nov 15, 2024 · 1 comment

Comments

@mmmarcos
Copy link
Contributor

The most common file time stamps are:

  • atime: last access time, updated on file read
  • mtime: last modified time, updated on file content change
  • ctime: changed time, updated on file metadata change
  • crtime (aka btime, birth or birth time): created time, updated on file creation
    • This last one is not POSIX, so it differs from platforms/filesystems

Internally, Parsec only handles created and updated file timestamps, which makes some timestamps not handled as they should.

For example, in Linux:

parsec-cloud/libparsec/crates/platform_mountpoint/src/unix/filesystem.rs

Lines 103 to 106 in 7059f9b

atime: updated,
mtime: updated,
ctime: updated,
crtime: created,

It might make sense to rethink Parsec data model to properly manage the 4 file timestamps instead of created/updated like we do at the moment.
@mmmarcos
Copy link
Contributor Author

mmmarcos commented Nov 15, 2024 •
edited
Loading

This was discussed with @vxgmichel in #5694

@mmmarcos mmmarcos mentioned this issue Nov 15, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mmmarcos