restoring from a full backup with errors - Error system failure: Negative seek offset

[fyd]

I have a situation, have a full backup that was completed with errors (failed due to insufficient space in disk). Now this backup is quite large and from details I see that some 50 accounts has been failed, and all others completed successfully.

The account I am trying to restore is NOT in the failed ones so I tried restoring the regular way only to get this error.

Error occurred: system failure: Negative seek offset

I looked into mailbox.log for these activities.

[root@zimbra ~]#
2011-06-11 12:26:29,338 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] backup - Account acc: All pending file IO completed (0 out of 0)
2011-06-11 12:26:29,340 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] index - Initialized Index for mailbox 3026 directory: LuceneIndex at com.zimbra.cs.index.Z23FSDirectory@/opt/zimbra/index/0/3026/index/0 Analyzer=com.zimbra.cs.index.ZimbraAnalyzer@287229 69
2011-06-11 12:26:29,340 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] cache - initializing folder and tag caches for mailbox 3026
2011-06-11 12:26:29,342 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] mbxmgr - Mailbox 3026 account d357abed-bb30-4d26-8e12-c2de041c8dd5 LOADED
2011-06-11 12:26:29,342 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] backup - Cleaning up data from failed restore (mid=3026)
2011-06-11 12:26:29,391 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] mailbox - clearing contents of mailbox 3026, group 26
2011-06-11 12:26:29,601 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] mbxmgr - Mailbox for account d357abed-bb30-4d26-8e12-c2de041c8dd5 DELETED
2011-06-11 12:26:29,603 WARN [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [name=acc;mid=3026;ip=127.0.0.1;] backup - Error occurred during restore account acc (2aa9245f-12dc-4a6e-9fea-fc6f81574095)
at com.zimbra.cs.backup.FileBackupTarget$RestoreAcctS ession.loadBlob(FileBackupTarget.java:2311)
at com.zimbra.cs.backup.RestoreAccountSession.loadBlo bsImpl(RestoreAccountSession.java:811)
at com.zimbra.cs.backup.FileBackupTarget$RestoreAcctS ession.loadBlobs(FileBackupTarget.java:2228)
at com.zimbra.cs.backup.RestoreAccountSession.startRe store(RestoreAccountSession.java:209)
at com.zimbra.cs.backup.FileBackupTarget.restore(File BackupTarget.java:480)
at com.zimbra.cs.backup.BackupManager.restore(BackupM anager.java:804)
at com.zimbra.cs.service.backup.Restore.handle(Restor e.java:138)
2011-06-11 12:26:29,604 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [ip=127.0.0.1;] io - AsyncFileCopier is shut down
2011-06-11 12:26:29,606 INFO [btpool0-511://localhost:7071/service/admin/soap/RestoreRequest] [ip=127.0.0.1;] SoapEngine - handler exception
ExceptionId:btpool0-511://localhost:7071/service/admin/soap/RestoreRequest:1307787989606:be6d136ae9229b46
at com.zimbra.cs.service.backup.Restore.handle(Restor e.java:153)
at com.zimbra.cs.backup.FileBackupTarget$RestoreAcctS ession.loadBlob(FileBackupTarget.java:2311)
at com.zimbra.cs.backup.RestoreAccountSession.loadBlo bsImpl(RestoreAccountSession.java:811)
at com.zimbra.cs.backup.FileBackupTarget$RestoreAcctS ession.loadBlobs(FileBackupTarget.java:2228)
at com.zimbra.cs.backup.RestoreAccountSession.startRe store(RestoreAccountSession.java:209)
at com.zimbra.cs.backup.FileBackupTarget.restore(File BackupTarget.java:480)
at com.zimbra.cs.backup.BackupManager.restore(BackupM anager.java:804)
at com.zimbra.cs.service.backup.Restore.handle(Restor e.java:138)
[root@zimbra ~]#
------------

I have tried using --ignoreredologs and -c switches under zmrestore, with no success.

I need to fix the error in the particular full backup and use it again. Can anyone help me please?? Pleeez! Ty.