A customer with a 230 GB mailbox has been getting an error when doing a search:
whatever the search, an error pops up.
I did a zxsuite hsm doCheckBlobs start mailbox_ids on his mailbox, and it found 2 missing blobs, both located on an HSM volume(hosted in an AWS S3 bucket)
Now I see If I want to recover from this error I should be doing zxsuite hsm doCheckBlobs start missing_blob_delete_item true
to delete the missing blobs from the DB.
I'm reluctant to do it on the HSM volume, as
- the S3 bucket is huge (1 TB) so that would take days.
- I read on this forum that it might lead to a much worse situation: ZBUG-3675: zmblobchk Errors with S3 HSM Storage - Zimbra 10.0.8 NE: viewtopic.php?t=72882
So this a dilemma:
The user is getting impatient because he can't search his mailbox, but I don't want to jeopardize the HSM volume on AWS S3.
Is there any other way to do that that does not involve the entire HSM volume on S3, can i limit the doCheckBlobs start missing_blob_delete_item
to a single mailbox?
Fran
whatever the search, an error pops up.
Code:
CriticalA network service error has occurred.method:[unknown]msg:system failure: java.lang.RuntimeException: com.zimbra.cs.mailbox.MailServiceException: No such blob: mailbox=53, item=2499544, change=2496755 ExceptionId:qtp2145970759-846:https://zmail2.his.com/service/soap/SearchRequest:1739998431620:cf470d2de9263290 Code:mail.NO_SUCH_BLOB Arg:(itemId, IID, "2499544") Arg:(ver, NUM, "2496755")code:service.FAILUREdetail:soap:Receivertrace:qtp2145970759-846:1739998431620:cf470d2de9263290Code:
2025-02-20 21:08:27,396 WARN Missing Blob file: Mailbox id: 53 - Item id: 2499544 - Revision: 2496755 - Blob path: /hsm/hsm2-a0ee6b66-ad4b-4c8c-b9b9-f80804cc00af/53/2499544-2496755.msg - Size: 3797460 - Digest: ,sdQu9QiJBZqbfJAjJK4GiRHwvQafFQV2iHAz65Jfis=2025-02-20 21:09:39,777 WARN Missing Blob file: Mailbox id: 53 - Item id: 2509249 - Revision: 2509228 - Blob path: /hsm/hsm2-a0ee6b66-ad4b-4c8c-b9b9-f80804cc00af/53/2509249-2509228.msg - Size: 15042 - Digest: R1Z6vJGJh1RUybJ8f1GCxcQFBCQSjavu6a8kjtFFyHg=to delete the missing blobs from the DB.
I'm reluctant to do it on the HSM volume, as
- the S3 bucket is huge (1 TB) so that would take days.
- I read on this forum that it might lead to a much worse situation: ZBUG-3675: zmblobchk Errors with S3 HSM Storage - Zimbra 10.0.8 NE: viewtopic.php?t=72882
So this a dilemma:
The user is getting impatient because he can't search his mailbox, but I don't want to jeopardize the HSM volume on AWS S3.
Is there any other way to do that that does not involve the entire HSM volume on S3, can i limit the doCheckBlobs start missing_blob_delete_item
to a single mailbox?
Fran
Statistics: Posted by hisfran — Sun Feb 23, 2025 8:33 pm