From: <bac...@li...> - 2004-09-15 10:43:09
|
====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000104 ====================================================================== Reported By: kardel Assigned To: ====================================================================== Project: bacula Bug ID: 104 Category: Storage Daemon Reproducibility: have not tried Severity: major Priority: normal Status: new ====================================================================== Date Submitted: 09-10-2004 23:17 PDT Last Modified: 09-15-2004 03:48 PDT ====================================================================== Summary: EOF handling stopped working? Description: tonights full backup failed to complete because it hits EOF on the tape. 1.35.2 was handNling the situation as expected. On 1.35.3 I see a "Network send error" and a backup job in error state after that. I will re-run the job to check whether it is reproducable and if it fails again i will downgrade to 1.35.2 a see what that does. ====================================================================== ---------------------------------------------------------------------- kardel - 09-11-2004 03:01 PDT ---------------------------------------------------------------------- Second attempt lead to a similar result. There are no core dumps. pip-dir: Start Backup JobId 95, Job=System.2004-09-11_08.14.08 pip-sd: Spooling data ... pip-sd: User specified spool size reached. pip-sd: Writting spooled data to Volume. Despooling 16,000,014,081 bytes ... pip-sd: System.2004-09-11_08.14.08 Fatal error: Cannot write block. Device at EOM. pip-sd: System.2004-09-11_08.14.08 Fatal error: Fatal device error: ERR=dev.c:1152 ioctl MTWEOF error on /dev/nrst0. ERR=Input/output error. pip-fd: System.2004-09-11_08.14.08 Fatal error: backup.c:470 Network send error. pip-dir: System.2004-09-11_08.14.08 Error: Bacula 1.35.3 (09Sep04): 11-Sep-2004 10:43 JobId: 95 Job: System.2004-09-11_08.14.08 Backup Level: Full Client: pip-fd FileSet: "all ffs" 2004-08-31 01:09:20 Pool: "Default" Start time: 11-Sep-2004 08:14 End time: 11-Sep-2004 10:43 FD Files Written: 589,625 SD Files Written: 589,625 FD Bytes Written: 15,872,576,269 SD Bytes Written: 15,961,142,780 Rate: 1766.0 KB/s Software Compression: 38.0 % Volume name(s): Volume Session Id: 3 Volume Session Time: 1094854872 Last Volume Bytes: 20,401,852,896 Non-fatal FD errors: 0 SD Errors: 0 FD termination status: Error SD termination status: Error Termination: *** Backup Error *** I now went back to 1.35.2 to see what happens now. Volume BACULA-0002 was marked Error as following error occured with 1.35.2 11-Sep-2004 11:51 pip-sd: System.2004-09-11_11.48.44 Error: Unable to position to end of data on device "/dev/nrst0". ERR=dev.c:477 ioctl MTEOM error on /dev/nrst0. ERR=Input/output error. 11-Sep-2004 11:51 pip-sd: Marking Volume "BACULA-0002" in Error in Catalog. I am no looking forward to see what happens at next EOM. ---------------------------------------------------------------------- kardel - 09-11-2004 06:24 PDT ---------------------------------------------------------------------- well, 1.35.2 won't work either... reverting back to 1.35.1 (stand by) 11-Sep-2004 13:18 pip-sd: User specified spool size reached. 11-Sep-2004 13:18 pip-sd: Writting spooled data to Volume. Despooling 16,000,013,563 bytes ... * * *pip-sd: spool.c:375 Bad return from despool in write_block. 11-Sep-2004 14:36 pip-sd: System.2004-09-11_11.48.44 Error: block.c:572 Write error at 5:9339 on device /dev/nrst0. ERR=Input/output error. 11-Sep-2004 14:36 pip-sd: System.2004-09-11_11.48.44 Fatal error: dev.c:1152 ioctl MTWEOF error on /dev/nrst0. ERR=Input/output error. 11-Sep-2004 14:36 pip-sd: System.2004-09-11_11.48.44 Fatal error: Fatal device error: ERR=dev.c:1152 ioctl MTWEOF error on /dev/nrst0. ERR=Input/output error. 11-Sep-2004 14:36 pip-fd: System.2004-09-11_11.48.44 Fatal error: backup.c:470 Network send error. 11-Sep-2004 14:36 pip-dir: System.2004-09-11_11.48.44 Error: Bacula 1.35.2 (30Aug04): 11-Sep-2004 14:36 JobId: 96 Job: System.2004-09-11_11.48.44 Backup Level: Full Client: pip-fd FileSet: "all ffs" 2004-08-31 01:09:20 Pool: "Default" Start time: 11-Sep-2004 11:48 End time: 11-Sep-2004 14:36 FD Files Written: 589,632 SD Files Written: 589,632 FD Bytes Written: 15,872,581,513 SD Bytes Written: 15,961,151,963 Rate: 1577.9 KB/s Software Compression: 38.0 % Volume name(s): BACULA-0000 Volume Session Id: 1 Volume Session Time: 1094896095 Last Volume Bytes: 4,060,904,223 Non-fatal FD errors: 0 SD Errors: 0 FD termination status: Error SD termination status: Error Termination: *** Backup Error *** ---------------------------------------------------------------------- kardel - 09-11-2004 10:01 PDT ---------------------------------------------------------------------- bacula 1.35.1 works as expected: 11-Sep-2004 18:22 pip-sd: System.2004-09-11_15.20.14 Error: block.c:566 Write error at 4:964 on device /dev/nrst0. ERR=Input/output error. 11-Sep-2004 18:22 pip-sd: System.2004-09-11_15.20.14 Error: dev.c:1152 ioctl MTWEOF error on /dev/nrst0. ERR=Input/output error. 11-Sep-2004 18:22 pip-sd: System.2004-09-11_15.20.14 Error: dev.c:1152 ioctl MTWEOF error on /dev/nrst0. ERR=Input/output error. 11-Sep-2004 18:22 pip-sd: System.2004-09-11_15.20.14 Error: Re-read of last block failed. Last block=62963 Current block=62963. 11-Sep-2004 18:22 pip-sd: End of medium on Volume "BACULA-0003" Bytes=4,061,932,394 Blocks=62,964 at 11-Sep-2004 18:22. 11-Sep-2004 18:23 pip-dir: Recycled volume "BACULA-0004" 11-Sep-2004 18:23 pip-sd: Please mount Volume "BACULA-0004" on Storage Device "SDT10000" for Job System.2004-09-11_15.20.14 So it seems EOM detection / EOF errorhandling changed between 1.35.1 to 1.35.2. Bug History Date Modified Username Field Change ====================================================================== 09-10-04 23:17 kardel New Bug 09-11-04 03:01 kardel Bugnote Added: 0000226 09-11-04 06:24 kardel Bugnote Added: 0000227 09-11-04 10:01 kardel Bugnote Added: 0000228 09-15-04 03:48 Dan Langille Severity feature => major ====================================================================== |