diff --git a/doc/bugs/__34__Missing_location__34___with_partsize__39__d_uploads/comment_2_c3d33e26fbefbef400f219a542cff7fb._comment b/doc/bugs/__34__Missing_location__34___with_partsize__39__d_uploads/comment_2_c3d33e26fbefbef400f219a542cff7fb._comment
new file mode 100644
index 0000000000..5964e72df4
--- /dev/null
+++ b/doc/bugs/__34__Missing_location__34___with_partsize__39__d_uploads/comment_2_c3d33e26fbefbef400f219a542cff7fb._comment
@@ -0,0 +1,21 @@
+[[!comment format=mdwn
+ username="kdm9"
+ avatar="http://cdn.libravatar.org/avatar/b7b736335a0e9944a8169a582eb4c43d"
+ subject="comment 2"
+ date="2024-07-19T13:11:05Z"
+ content="""
+For future google searchers:
+
+When interfacing with Ceph storage via the S3 backend, I get errors like the following on larger files
+
+`XmlException {xmlErrorMessage = \"Missing ETag\"}`
+
+
+Like above, these 'errors' are actually successes with a non-compliant S3 backend that is missing either the Location or Etag file.
+
+
+I confirm that setting partsize > chunk works around this issue, in my case `chunk=4GiB partsize=5GiB`.
+
+Best,
+Kevin
+"""]]