system failure: Unable to copy 142:257:7[1] to volume 3 ExceptionId:BlobMover

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
fbzimblet
Advanced member
Advanced member
Posts: 119
Joined: Sun Apr 17, 2016 4:15 pm

system failure: Unable to copy 142:257:7[1] to volume 3 ExceptionId:BlobMover

Post by fbzimblet »

my zmhsm status seems failed and I'm not sure if it is related with using NFS?

Code: Select all

[zimbra@mail ~]$ zmhsm -u
Last HSM Session Stats
----------------------
Start time: Fri Oct 21 21:55:25 MYT 2016
End time:   Fri Oct 21 21:55:25 MYT 2016
Query :before:-30day
Not currently running.
An error occurred: com.zimbra.common.service.ServiceException: system failure: Unable to copy 142:257:7[1] to volume 3 ExceptionId:BlobMover:1477058125748:a831dc752d778322 Code:service.FAILURE
Moved 0 blobs to volume 3.
fbzimblet
Advanced member
Advanced member
Posts: 119
Joined: Sun Apr 17, 2016 4:15 pm

Re: system failure: Unable to copy 142:257:7[1] to volume 3 ExceptionId:BlobMover

Post by fbzimblet »

nobody had this issue before?

zcs NE 7.1.4 on Centos 5
phoenix
Ambassador
Ambassador
Posts: 27278
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Re: system failure: Unable to copy 142:257:7[1] to volume 3 ExceptionId:BlobMover

Post by phoenix »

I guess that nobody has had this problem recently but my usual question applies, did you search the forums first? If you search for 'ExceptionId:BlobMover" you'll find the one thread that mentions your problem other than that I'd suggest opening a support ticket, assuming you have a valid support contract. If that really is the version of ZCS that you're running I'd suggest for your security, and that of your users, you upgrade to ZCS 8.7 as there are security vulnerabilities in earlier versions. ;)
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra
fbzimblet
Advanced member
Advanced member
Posts: 119
Joined: Sun Apr 17, 2016 4:15 pm

Re: system failure: Unable to copy 142:257:7[1] to volume 3 ExceptionId:BlobMover

Post by fbzimblet »

thanks for the tip @phoenix

I changed hsm folder's permission to 750 then it works now

Code: Select all

# chmod 750 /backupzimbra/hsm/

# su - zimbra

$ zmhsm -t
HSM process started.

$ zmhsm -u
Current HSM Session Stats
-------------------------
Start time: Mon Oct 24 13:33:01 MYT 2016
Query :before:-30day
Currently running.
Moved 99 blobs to volume 3.
Mailboxes processed: 2 out of 64.
phoenix
Ambassador
Ambassador
Posts: 27278
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Re: system failure: Unable to copy 142:257:7[1] to volume 3 ExceptionId:BlobMover

Post by phoenix »

I'm glad you've fixed it. :)
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra
Post Reply