[GH-ISSUE #604] s3fs 1.82 version failing #341

New issue

Closed

opened 2026-03-04 01:44:32 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @vgadhadaran on GitHub (May 18, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/604

Originally created by @vgadhadaran on GitHub (May 18, 2017). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/604

kerem closed this issue

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

kerem commented

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

Author

Owner

@gaul commented on GitHub (May 18, 2017):

Which S3 implementation do you use? Multi-part upload fails:

May 18 13:05:05 k0002414 s3fs[3337]: computing signature [POST] [/archivetest/test100g.sas7bdat.R] [uploads=] []
May 18 13:05:05 k0002414 s3fs[3337]: url is https://awspoc.hcpdevn1.travt.net
May 18 13:05:05 k0002414 s3fs[3337]: HTTP response code 501

Try working around this with -o nomultipart.

@gaul commented on GitHub (May 18, 2017): Which S3 implementation do you use? Multi-part upload fails: ``` May 18 13:05:05 k0002414 s3fs[3337]: computing signature [POST] [/archivetest/test100g.sas7bdat.R] [uploads=] [] May 18 13:05:05 k0002414 s3fs[3337]: url is https://awspoc.hcpdevn1.travt.net May 18 13:05:05 k0002414 s3fs[3337]: HTTP response code 501 ``` Try working around this with `-o nomultipart`.

kerem referenced this issue

2026-03-04 01:54:07 +03:00

[PR #341] [MERGED] Fix the memory leak issue in fdcache. #1470