From: <bac...@li...> - 2007-02-27 09:44:19
|
The following issue requires your FEEDBACK. ====================================================================== http://bugs.bacula.org/view.php?id=790 ====================================================================== Reported By: wolfmair Assigned To: ====================================================================== Project: bacula Issue ID: 790 Category: Director Reproducibility: always Severity: minor Priority: normal Status: feedback ====================================================================== Date Submitted: 02-22-2007 11:32 EST Last Modified: 02-27-2007 04:44 EST ====================================================================== Summary: File truncated on restore Description: /part2/usr/lib/libGLU.so.1.3 0-Feb 15:16 linux-install-fd: RestoreFiles.2007-02-20_15.10.05 Error: attribs.c:409 File size of restored file /part2/usr/lib/libGLU.so.1.3 not correct. Original 573295, restored 1376259. This is the only file out of 12000 which caused an error. The original file size on the system is 573295. I've tried to restore that file with file daemon 2.0.2 and 1.38.11 with the same error. Then I did a new backup of the file and with that new backup the restore is ok. Although the backup client has not changed between these two backup runs. So unfortunately I can tell you what to do to reproduce this. If I restore from that certain backup it fails all the time but restore from the newer backup runs fine all the time. Can I extract something out of the image file which might be helpful? ====================================================================== ---------------------------------------------------------------------- kern - 02-27-07 04:44 ---------------------------------------------------------------------- If I understand this correctly, the error occurs every time that you restore from one specific backup. However, you are unable to reproduce the error in any new backups. Is that correct? Assuming the above is the case: To fix the problem, I really need something that is reproducible. One could *possibly* find the source of the problem by carefully examining the backup data, but given that I have never seen this before, I am inclined to think that you have or had some hardware error. I suggest you search your system logs and see if there were any errors reported at the time the backup was being made. You haven't mentioned what version of the OS you are using or whether it is a tape/disk backup. There was a kernel SCSI driver bug in SuSE 10.1 that could very easily have caused this. Issue History Date Modified Username Field Change ====================================================================== 02-22-07 11:32 wolfmair New Issue 02-27-07 04:44 kern Note Added: 0002256 02-27-07 04:44 kern Status new => feedback ====================================================================== |