You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempted to copy a file to the bucket throws i/o error when closing the file. The file is actually well-written (verified by sha256sum checksum).
cp -f testfile_100M.bin /my_local_dir/
cp: overwrite ‘/my_local_dir/testfile_100M.bin’? y
cp: failed to close ‘/my_local_dir/testfile_100M.bin’: Input/output error
Relevant log output
2024-12-11T16:42:13.040462Z WARN getxattr{req=6 ino=2 name="security.capability"}: mountpoint_s3::fuse: getxattr failed: operation not supported by Mountpoint
2024-12-11T16:42:13.040554Z WARN removexattr{req=7 ino=2 name="security.ima"}: mountpoint_s3::fuse: removexattr failed: operation not supported by Mountpoint
2024-12-11T16:42:13.318212Z WARN put_object_single{id=8 bucket="mybucket" key="testfile_100M.bin"}: mountpoint_s3_client::s3_crt_client: duration=73.368095ms request_id=tx00000af56083bb51794bc-006759c0e5-92f3e-default error=ServiceError(PreconditionFailed) meta request failed
2024-12-11T16:42:13.327727Z WARN flush{req=1609 ino=2 fh=1 pid=12097 name="testfile_100M.bin"}: mountpoint_s3::fuse: flush failed: put failed: put request failed: Service error: At least one of the pre-conditions you specified did not hold
The text was updated successfully, but these errors were encountered:
Hello, thank you for making this report. From the logs, it appears that your S3 implementation is returning a 412 precondition failed response to Mountpoint. Running with --debug --debug-crt should help verify that.
Mountpoint for Amazon S3 version
mount-s3 1.13.0
AWS Region
NA
Describe the running environment
A Centos7 vm connecting to a non-AWS S3 provider, based on OpenStack and CEPH
Mountpoint options
What happened?
Attempted to copy a file to the bucket throws i/o error when closing the file. The file is actually well-written (verified by sha256sum checksum).
Relevant log output
The text was updated successfully, but these errors were encountered: