mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #14] s3fs -u should return 0 if there are no lost multiparts #7
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#7
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 @timurb on GitHub (Feb 18, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/14
I think s3fs should return 0 in the case of successful operation (no matter if there are any lost multiparts or not and if they were deleted or not) and non-0 otherwise (i.e. on errors). Currently it looks like you can't distinguish easily between s3fs errors and no lost multiparts.
I don't insist my vision is the only correct one but just wanted to hear of other opinions on this matter.
@ggtakec commented on GitHub (Mar 3, 2014):
Thanks a bug report and sorry for replying too late.
#20 pull request is merged master branch.
It works good fixed for this problem.
Thanks in advance.