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.

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

[BUG] ctime, mtime, atime of files and directories are lost in SMB external storage #44389

Open
ShGKme opened this issue Mar 21, 2024 · 4 comments
Assignees
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 27-feedback bug feature: external storage feature: filesystem hotspot: file time handling ctime, mtime, etc. handling during various operations

Comments

@ShGKme
Copy link
Contributor

ShGKme commented Mar 21, 2024

How to use GitHub

  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce:

  1. Add an SMB storage via files_external
  2. Sync the storage to desktop folder
  3. Move data from Nextcloud storage to files_external storage via synced folder
  4. Files first have original timestamps until data on files_external is rediscovered
@ShGKme ShGKme added bug 1. to develop Accepted and waiting to be taken care of feature: external storage labels Mar 21, 2024
@szaimen

This comment was marked as resolved.

@szaimen szaimen added needs info 0. Needs triage Pending check for reproducibility or if it fits our roadmap and removed 1. to develop Accepted and waiting to be taken care of labels Mar 21, 2024
@ShGKme

This comment was marked as resolved.

@sorbaugh
Copy link
Contributor

sorbaugh commented Apr 12, 2024

cc @jancborchardt , the more we analyze this issue the more questions pop up. For instance, COPY operations change the mtime of the file. Do we have a reason for this? Wouldn't it be better for COPY moves to leave the mtime unchanged?

Also cc-ing @Altahrim & @come-nc to join the discussion

@jancborchardt
Copy link
Member

@sorbaugh at least from design side there is no reason for this, no. It’s also weird because if you are in a folder sorted by date and copy/duplicate a file, both files would be far away from each other, whereas they should be right next to each other.

@joshtrichards joshtrichards added feature: filesystem hotspot: file time handling ctime, mtime, etc. handling during various operations labels Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 27-feedback bug feature: external storage feature: filesystem hotspot: file time handling ctime, mtime, etc. handling during various operations
Projects
None yet
Development

No branches or pull requests

6 participants