starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #500] HTTP response code 409 error #282

New issue

Closed

opened 2026-03-04 01:44:00 +03:00 by kerem · 6 comments

kerem commented

2026-03-04 01:44:00 +03:00

Owner

Originally created by @vgadhadaran on GitHub (Nov 16, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/500

I am trying to move the file however getting the below error

[root@k8002180 abc]# mv 500m1 /tmp/s3demo
mv: preserving times for `/tmp/s3demo/500m1': Input/output error
mv: closing `/tmp/s3demo/500m1': Input/output error

Digging at the log file I am seeing the response code return i 409 . how to fix this?

[

Originally created by @vgadhadaran on GitHub (Nov 16, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/500 I am trying to move the file however getting the below error ``` [root@k8002180 abc]# mv 500m1 /tmp/s3demo mv: preserving times for `/tmp/s3demo/500m1': Input/output error mv: closing `/tmp/s3demo/500m1': Input/output error ``` Digging at the log file I am seeing the response code return i 409 . how to fix this? [

kerem closed this issue

2026-03-04 01:44:00 +03:00

kerem commented

2026-03-04 01:44:01 +03:00

Author

Owner

@gaul commented on GitHub (Nov 16, 2016):

Do you use Hitachi S3 storage? You may have encountered an issue where HCP does not support overwriting existing objects. #436 tracks a similar issue.

@gaul commented on GitHub (Nov 16, 2016): Do you use Hitachi S3 storage? You may have encountered an issue where HCP does not support overwriting existing objects. #436 tracks a similar issue.

kerem commented

2026-03-04 01:44:01 +03:00

Author

Owner

@vgadhadaran commented on GitHub (Nov 17, 2016):

yes, its hitachi. however I am getting this error when trying to move the data for first time and not overwriting it.

@vgadhadaran commented on GitHub (Nov 17, 2016): yes, its hitachi. however I am getting this error when trying to move the data for first time and not overwriting it.

kerem commented

2026-03-04 01:44:01 +03:00

Author

Owner

@ggtakec commented on GitHub (May 5, 2017):

@vgadhadaran @andrewgaul
Please see my #436 comment, I think HCP can not over write any object when the versioning is not enabled.

@ggtakec commented on GitHub (May 5, 2017): @vgadhadaran @andrewgaul Please see my #436 comment, I think HCP can not over write any object when the versioning is not enabled.

kerem commented

2026-03-04 01:44:02 +03:00

Author

Owner

@ggtakec commented on GitHub (May 9, 2017):

#436 was closed, solve this issue by enable versioning on HCP.

@ggtakec commented on GitHub (May 9, 2017): #436 was closed, solve this issue by enable versioning on HCP.

kerem commented

2026-03-04 01:44:02 +03:00

Author

Owner

@vgadhadaran commented on GitHub (May 10, 2017):

versioning enabled but still the same issue

@vgadhadaran commented on GitHub (May 10, 2017): versioning enabled but still the same issue

kerem commented

2026-03-04 01:44:02 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 30, 2019):

We kept this issue open for a long time.
Is this problem continuing?
We launch new version 1.86, which fixed some problem(bugs).
Please use the latest version.
I will close this, but if the problem persists, please reopen or post a new issue.

@ggtakec commented on GitHub (Mar 30, 2019): We kept this issue open for a long time. Is this problem continuing? We launch new version 1.86, which fixed some problem(bugs). Please use the latest version. I will close this, but if the problem persists, please reopen or post a new issue.

kerem referenced this issue

2026-03-04 02:01:04 +03:00

[PR #588] [MERGED] Default transport to HTTPS #1563