Noel Lucas

Adding this extra debug logging from this morning: [root@centos8s hcpdata]# s3fs testns -o use_cache=/tmp -o use_path_request_style -o allow_other -o no_check_certificate -o multireq_max=5 -o passwd_file=/etc/s3fs-passwd -o dbglevel=info -f -o curldbg /hcpdata...

I added my SSL certificate to the bundle in /etc/pki/tls/certs/ca-bundle.crt and tried again with these results: [root@centos8s hcpdata]# s3fs testns -o use_cache=/tmp -o use_path_request_style -o allow_other -o multireq_max=5 -o passwd_file=/etc/s3fs-passwd...

FYI, I just tested and versions 1.85, 1.87, and 1.89 work FINE with NO issue.

I tested the latest 1.93 against our HCP Cloudscale Product and it works with no problem, but not our HCP product. Both are SIGV4 compliant.

@ggtakec Correct, (2) also gave the IO error. (3) also gave the IO error. Note that I said above "FYI, I just tested and versions 1.85, 1.87, and 1.89 work...

@ggtakec Thanks for the followup. I just tested 1.94 against our HCP platform and it still gives the error: -bash: cd: /hcpdata: Input/output error This error is AFTER mounting the...

S3FS Version: 1.94-1.el9 Log from S3FS: [root@localhost ~]# s3fs testns -o use_cache=/tmp -o use_path_request_style -o allow_other -o multireq_max=5 -o no_check_certificate -o passwd_file=/etc/passwd-s3fs -o dbglevel=info -f -o curldbg /hcpdata -o url=https://testtenant.hcp1.demo.com/...

@juliusv

Same exact issue here. Using the command shown: docker run --name=merge -v /my/input:/input -v /my/output:/output ghcr.io/djdembeck/m4b-merge:main