mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #145] rename_before_close failure #87
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#87
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gaul on GitHub (Mar 9, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/145
@kahing Can you investigate?
@gaul commented on GitHub (Mar 9, 2015):
Note that I tested with s3proxy-1.4.0-20150307.195914-6-jar-with-dependencies.jar, not 1.3.0 release.
@kahing commented on GitHub (Mar 9, 2015):
I got failure before it gets to that test:
Looking...
@gaul commented on GitHub (Mar 9, 2015):
Sorry we need to merge #147 to avoid the first set of failures.
@kahing commented on GitHub (Mar 9, 2015):
confirmed that #147 fixes the first rename problem. confirmed that the rename_before_close test fails with real S3 as well
@kahing commented on GitHub (Mar 9, 2015):
regression caused by #138. Reverting the no_cache prefix changes fixes this problem.
I am not sure what the no_cache prefix change is intended to fix, why wouldn't we always want to use the same FdEntity?
@ggtakec commented on GitHub (Mar 10, 2015):
@kahing I meged fixed code to master branch now.
This problem is occurred by s3fs does not have fsync handler. so fsync event could not be caught by s3fs.
Before #138, s3fs could not disable the use_cache, in order to have continued to share the file handle, had happened fsync functions. After fixing #138, poblem of this issue was apparent.
Probably #150 fixed this issue.
@andrewgaul @kahing thanks a lot.
if this merge can fix all of this issue, please close this issue.
Regards,
@ggtakec commented on GitHub (Mar 21, 2015):
I close this issue.
If you continue to not solve this problem, please reopen this issue.
Thanks a lot.
@kahing commented on GitHub (Apr 9, 2015):
master still fails the rename_before_close test
@gaul commented on GitHub (Apr 24, 2015):
@ggtakec Please reopen this issue -- we lack the karma to do so.
@ggtakec commented on GitHub (Jan 20, 2019):
#898 has been merged.