ERRORS system: FileUtil.copy incomplete transfer

[rotorboy]

Greetings.

Everything seemed to be going along fine then last night an error occurred in the normal backups (Below). Any ideas what to do about this?

(/opt/zimbra/redolog/archive/redo-20110727.080029.277-seq1231.log,/backup/tmp/incr-20110727.080009.630/redologs/redo-20110727.080029.277-seq1231.log): incomplete transfer; expected=524288 bytes, actual=262144 bytes
java.io.IOException: FileUtil.copy(/opt/zimbra/redolog/archive/redo-20110727.080029.277-seq1231.log,/backup/tmp/incr-20110727.080009.630/redologs/redo-20110727.080029.277-seq1231.log): incomplete transfer; expected=524288 bytes, actual=262144 bytes
at com.zimbra.common.util.FileUtil.copy(FileUtil.java :170)
at com.zimbra.common.util.FileUtil.copy(FileUtil.java :56)
at com.zimbra.cs.backup.FileBackupTarget$FileBackupSe t.backupRedoLogs(FileBackupTarget.java:1328)
at com.zimbra.cs.backup.BackupSet.startIncrementalBac kup(BackupSet.java:812)
at com.zimbra.cs.backup.FileBackupTarget$FileBackupSe t.startIncrementalBackup(FileBackupTarget.java:108 8)
at com.zimbra.cs.backup.BackupManager.backupIncrement al(BackupManager.java:327)
at com.zimbra.cs.service.backup.Backup.handleNetworkR equest(Backup.java:152)
at com.zimbra.cs.service.NetworkDocumentHandler.handl e(NetworkDocumentHandler.java:23)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:287)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:294)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:215)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:725)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:155)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:946)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)

[fyd]

Originally Posted by rotorboy

Greetings.

Everything seemed to be going along fine then last night an error occurred in the normal backups (Below). Any ideas what to do about this?

rotorboy, was the backup interrupted in anyway? Perhaps due to a lack of disk space in backup target.

[rotorboy]

I was wondering that too until I saw the drive stats:

Filesystem            Size  Used Avail Use% Mounted on
/dev/xvda3            289G   82G  192G  30% /
/dev/xvda1            190M   28M  153M  16% /boot
tmpfs                 4.9G     0  4.9G   0% /dev/shm
/dev/xvdb1            197G  108G   80G  58% /backup
192.168.1.3:/z1      927G  309G  618G  34% /bk1

The destination is the NFS bk1 partition. I do an rsync backup to the /backup as an extra precaution.

[fyd]

(/opt/zimbra/redolog/archive/redo-20110727.080029.277-seq1231.log,/backup/tmp/incr-20110727.080009.630/redologs/redo-20110727.080029.277-seq1231.log)

Okay. But why is it saying /backup/tmp/incr ..
Could it be that the backup program was no longer looking into the configured target place(/bk1), and worked with the default place (/backup)?
A break up of nfs connection perhaps.

[fyd]

Check you target location by running this command.

# su - zimbra
$ zmprov gacf | grep zimbraBackupTarget

[rotorboy]

my mistake... I recently changed it to /backup and use rsync to copy /backup to /bk1
So NFS is not being used by Zimbra.
Still, there's plenty of storage on /backup /opt/zimbra is only using 45GB.

[rotorboy]

[zimbra]$ zmprov gacf | grep zimbraBackupTarget
zimbraBackupTarget: /backup