moving mailboxes between Primary Volumes

[d0s0n]

ok, everytime I run it there's less space occupied on source volume, but it never move it completely.

I've run it 4 times and now there's 270m still remaining.

is this normal?

It can depend by some zimbra corruptions, you can check the consistency of your store with the zmblobchk command.

what kind of errors should I see in mailbox.log?

You should look for ZxPowerStore word and check if there were some exceptions related to the move blobs operation.

D0s0n

[muzzol]

i've executed zmblobchk -v start and there's a lot of unexpected blog errors:

Mailbox 126, volume 4, /opt/storage_synology_zimbra/0/126/msg/2/10805-10606.msg.bak: unexpected blob.  File size is 619129.

and just one of this:

com.zimbra.common.soap.SoapFaultException: no such account: bedeeea4-28d5-47dd-8324-224372904fec
ExceptionId:btpool0-1771://localhost:7071/service/admin/soap/CheckBlobConsistencyRequest:1358346294670:1142a0ab72ede351
Code:account.NO_SUCH_ACCOUNT
	at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:88)
	at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:354)
	at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:313)
	at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:260)
	at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:164)
	at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:407)
	at com.zimbra.common.soap.SoapTransport.invokeWithoutSession(SoapTransport.java:393)
	at com.zimbra.cs.account.soap.SoapProvisioning.invokeRequest(SoapProvisioning.java:342)
	at com.zimbra.cs.account.soap.SoapProvisioning.invoke(SoapProvisioning.java:350)
	at com.zimbra.cs.store.file.BlobConsistencyUtil.checkMailbox(BlobConsistencyUtil.java:207)
	at com.zimbra.cs.store.file.BlobConsistencyUtil.run(BlobConsistencyUtil.java:179)
	at com.zimbra.cs.store.file.BlobConsistencyUtil.main(BlobConsistencyUtil.java:282)

how can I repair those blob errors?

[Cine]

Hello muzzol!

The "unexpected blob" matter has been discussed on THIS thread...

I honestly have never seen the "com.zimbra.common.soap.SoapFaultException: no such account" error in this context, but my guess is that the blobcheck utility tried to access a nonexisting mailbox for some reason... What's the output of "zmprov ga bedeeea4-28d5-47dd-8324-224372904fec"?

Have a nice day,
Cine

[muzzol]

I get an error running zmdbintegrityreport:

/opt/zimbra/libexec/zmdbintegrityreport -m -v
-m emails report to admin account, otherwise report is presented on stdout
-v verbose output
-r attempt auto repair of tables
-h help

I tried without -m and this is the result:

$ /opt/zimbra/libexec/zmdbintegrityreport -v   
Database errors found.
/opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=XXXXXXXX
mysql.general_log
 Error    : You can't use locks with log tables.
 mysql.slow_log
 Error    : You can't use locks with log tables.

should I try with -r ?

[Cine]

I get an error running zmdbintegrityreport:

/opt/zimbra/libexec/zmdbintegrityreport -m -v
-m emails report to admin account, otherwise report is presented on stdout
-v verbose output
-r attempt auto repair of tables
-h help

Hello muzzol...

What error do you get?

Have a nice day,
Cine

[muzzol]

sorry I miscopied output.

the error is Options -m and -v are mutually exclusive

$ /opt/zimbra/libexec/zmdbintegrityreport -m -v
Options -m and -v are mutually exclusive
Usage: /opt/zimbra/libexec/zmdbintegrityreport [-m] [-v] [-h] [-r]
-m emails report to admin account, otherwise report is presented on stdout
-v verbose output
-r attempt auto repair of tables
-h help

I tried without -m and this is the result:
Code:

$ /opt/zimbra/libexec/zmdbintegrityreport -v   
Database errors found.
/opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=XXXXXXXX
mysql.general_log
 Error    : You can't use locks with log tables.
 mysql.slow_log
 Error    : You can't use locks with log tables.

should I try with -r ?

[Cine]

Hello muzzol,

the

mysql.general_log Error    : You can't use locks with log tables. 
mysql.slow_log Error    : You can't use locks with log tables.

error is caused by a MySQL bug and is neglectable... Is this the full output of the command or did more error appear?


Have a nice day,
Cine

[muzzol]

this is all.

I've launched again zmblobchk -v start and errors are still there.

I realized that all errors are from files with "msg.bak" suffix, is that something to take in account?

maybe a can just delete them.

[Cine]

Hello muzzol!

I suggest to run the zmblobchk with the "--unexpected-blob-list /path/to/list.txt" argument so that the list of alld unexpected BLOBs' paths is written on a file. You can then sample-check the files and eventually delete them...

Have a nice day,
Cine

[muzzol]

I've runned again volume command: zxsuite powerstore doVolumeToVolumeMove volum30g nfssynology


and here you can find related log: Ubuntu Pastebin