-
Notifications
You must be signed in to change notification settings - Fork 309
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
DAOS-15049 dfs: fix bug in setattr when mtime and size are being set #13640
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bug-tracker data: |
- in dfs_osetattr(), if user sets both mtime and size, the hlc for the mtime is not being update on storage. To fix that, use the hlc reported from the array_stat and update that when updating the mtime in the entry. Features: dfs Required-githooks: true Signed-off-by: Mohamad Chaarawi <[email protected]>
9daf9c9
to
0b1ec38
Compare
Test stage Functional Hardware Medium Verbs Provider completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-13640/2/execution/node/1434/log |
yuvale2
approved these changes
Jan 22, 2024
ashleypittman
approved these changes
Jan 22, 2024
daltonbohning
approved these changes
Jan 22, 2024
mchaarawi
added a commit
that referenced
this pull request
Jan 22, 2024
…13640) - in dfs_osetattr(), if user sets both mtime and size, the hlc for the mtime is not being update on storage. To fix that, use the hlc reported from the array_stat and update that when updating the mtime in the entry. Signed-off-by: Mohamad Chaarawi <[email protected]>
mchaarawi
added a commit
that referenced
this pull request
Jan 26, 2024
* DAOS-14474 dfs: remove unused --evict option from checker (#13616) The dfs fs check command already allows evicting containers using the --flags=evict option. the --evict option was added by mistake and does not do anything today, so remove it. * DAOS-14219 dfs: checker should not follow symlinks (#13625) The DFS checker should mark the symlink oid and not dereference the symlink value. the value can be invalid anyway and if a valid path in the container, it would be reachable from the hardlink path. * DAOS-14476 dfs: update root stbuf on lookup of root (#13597) - In order to avoid stale root stat data, update the root stbuf on lookup. - add mtime/ctime proper querying for dfs_lookup() - destroy the uns container after the link is remove since dfuse looks up the root if the container of being destroyed. * DAOS-15049 dfs: fix bug in setattr when mtime and size are being set (#13640) - in dfs_osetattr(), if user sets both mtime and size, the hlc for the mtime is not being update on storage. To fix that, use the hlc reported from the array_stat and update that when updating the mtime in the entry. Signed-off-by: Mohamad Chaarawi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Required-githooks: true
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: