Arno Lehmann wrote: > Hello, > > On 7/5/2006 10:19 AM, Julien Cigar wrote: > >> Hi ! >> >> === >> Bacula: 1.38.9-10 (with the Postgresql 8.1.4 backend), director >> configuration: http://mordor.ath.cx/stuff/bacula-dir.conf.html >> >> Kernel: 2.6.15 >> >> Tape: Host: scsi0 Channel: 00 Id: 06 Lun: 00 >> Vendor: SONY Model: SDX-500C Rev: 0204 >> Type: Sequential-Access ANSI SCSI revision: 02 >> >> Scsi: Adaptec AIC7xxx driver version: 7.0 >> Adaptec 2940 Ultra SCSI adapter >> aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs >> Allocated SCBs: 4, SG List Length: 128 >> >> === >> >> I got a little problem with my backup today : >> >> 05-Jul 03:00 phoenix-dir: Start Backup JobId 12, >> Job=bebif-job.2006-07-05_03.00.00 >> 05-Jul 05:36 phoenix-sd: bebif-job.2006-07-05_03.00.00 Error: block.c:538 >> Write error at 50:5589 on device "sony SDX-500C" (/dev/st0). >> ERR=Input/output error. >> > > Tape life time used up, or drive broken. Usually. After all, this is DDS > technology, right? > >
The tapes are new .. and the drive isn't too old I think. Do you think it could be a bad SCSI cable ? >> 05-Jul 05:36 phoenix-sd: bebif-job.2006-07-05_03.00.00 Error: Error writing >> final EOF to tape. This Volume may not be readable. >> > > This really is an error message, not only a warning. > Yep ... strange that the drive worked without problems from 3:00am to 5:36am ... > >> dev.c:1542 ioctl MTWEOF error on "sony SDX-500C" (/dev/st0). >> ERR=Input/output error. >> 05-Jul 05:36 phoenix-sd: End of medium on Volume "Full-Tape-0002" >> Bytes=48,606,123,849 Blocks=753,445 at 05-Jul-2006 05:36. >> 05-Jul 05:37 phoenix-dir: Created new Volume "Full-Tape-0003" in catalog. >> 05-Jul 05:37 phoenix-sd: Please mount Volume "Full-Tape-0003" on Storage >> Device "sony SDX-500C" (/dev/st0) for Job bebif-job.2006-07-05_03.00.00 >> 05-Jul 06:37 phoenix-sd: Please mount Volume "Full-Tape-0003" on Storage >> Device "sony SDX-500C" (/dev/st0) for Job bebif-job.2006-07-05_03.00.00 >> 05-Jul 07:38 phoenix-sd: bebif-job.2006-07-05_03.00.00 Warning: Director >> wanted Volume "Full-Tape-0003" for device "sony SDX-500C" (/dev/st0). >> Current Volume "Full-Tape-0002" not acceptable because: >> 1998 Volume "Full-Tape-0002" status is Full, but should be Append, >> Purged or Recycle. >> 05-Jul 08:38 phoenix-sd: Please mount Volume "Full-Tape-0003" on Storage >> Device "sony SDX-500C" (/dev/st0) for Job bebif-job.2006-07-05_03.00.00 >> >> *** I changed the volume status of Full-Tape-0002 from "Full" to "Append" >> > > That's what you made the final mistake. > Occasionally this manipulation worked in the past .. > >> 05-Jul 09:20 phoenix-sd: Volume "Full-Tape-0002" previously written, moving >> to end of data. >> 05-Jul 09:21 phoenix-sd: bebif-job.2006-07-05_03.00.00 Error: I cannot write >> on Volume "Full-Tape-0002" because: >> The number of files mismatch! Volume=61 Catalog=50 >> > > Yeah, sure... probably the volume info in the catalog was not correctly > upgraded after the failing WEOF, because this information is worthless > in such a situation. (Keep in mind that I did *not* check the code.) > > >> 05-Jul 09:21 phoenix-sd: Marking Volume "Full-Tape-0002" in Error in Catalog. >> 05-Jul 09:23 phoenix-sd: Please mount Volume "Full-Tape-0003" on Storage >> Device "sony SDX-500C" (/dev/st0) for Job bebif-job.2006-07-05_03.00.00 >> >> *** I updated the number of files in the catalog from 50 to 61 >> >> 05-Jul 09:37 phoenix-sd: Volume "Full-Tape-0002" previously written, moving >> to end of data. >> 05-Jul 09:39 phoenix-sd: Ready to append to end of Volume "Full-Tape-0002" >> at file=61. >> 05-Jul 09:39 phoenix-sd: New volume "Full-Tape-0002" mounted on device "sony >> SDX-500C" (/dev/st0) at 05-Jul-2006 09:39. >> 05-Jul 09:39 phoenix-sd: End of Volume "Full-Tape-0002" at 61:0 on device >> "sony SDX-500C" (/dev/st0). Write of 64512 bytes got -1. >> 05-Jul 09:39 phoenix-sd: bebif-job.2006-07-05_03.00.00 Error: Error writing >> final EOF to tape. This Volume may not be readable. >> dev.c:1542 ioctl MTWEOF error on "sony SDX-500C" (/dev/st0). >> ERR=Input/output error. >> > > Another indication that this tape is simply not writeable at that position. > > Any idea why ? Tape broken .. ? (The tape drive has been cleaned recently) >> 05-Jul 09:39 phoenix-sd: bebif-job.2006-07-05_03.00.00 Fatal error: >> append.c:207 Fatal append error on device "sony SDX-500C" (/dev/st0): >> ERR=dev.c:1542 ioctl MTWEOF error on "sony SDX-500C" (/dev/st0). >> ERR=Input/output error. >> 05-Jul 09:39 bebif-fd: bebif-job.2006-07-05_03.00.00 Fatal error: >> backup.c:500 Network send error to SD. ERR=Broken pipe >> 05-Jul 09:39 bebif-fd: bebif-job.2006-07-05_03.00.00 Error: bnet.c:257 Read >> error from Storage daemon:164.15.x.x:9103: ERR=Connection reset by peer >> 05-Jul 09:39 bebif-fd: bebif-job.2006-07-05_03.00.00 Error: bnet.c:426 Write >> error sending 65536 bytes to Storage daemon:164.15.x.x:9103: ERR=Broken pipe >> 05-Jul 09:39 phoenix-dir: bebif-job.2006-07-05_03.00.00 Error: Bacula 1.38.9 >> (02May06): 05-Jul-2006 09:39:38 >> JobId: 12 >> Job: bebif-job.2006-07-05_03.00.00 >> Backup Level: Full >> Client: "bebif-fd" >> i486-pc-linux-gnu,debian,testing/unstable >> FileSet: "bebif-fs" 2006-07-03 14:29:22 >> Pool: "full-tape-pool" >> Storage: "tape-st" >> Scheduled time: 05-Jul-2006 03:00:00 >> Start time: 05-Jul-2006 03:00:03 >> End time: 05-Jul-2006 09:39:38 >> Elapsed time: 6 hours 39 mins 35 secs >> Priority: 10 >> FD Files Written: 47,294 >> SD Files Written: 47,294 >> FD Bytes Written: 7,346,958,120 (7.346 GB) >> SD Bytes Written: 7,353,723,841 (7.353 GB) >> Rate: 306.4 KB/s >> Software Compression: None >> Volume name(s): Full-Tape-0002 >> Volume Session Id: 12 >> Volume Session Time: 1151910220 >> Last Volume Bytes: 48,606,123,849 (48.60 GB) >> Non-fatal FD errors: 2 >> SD Errors: 0 >> FD termination status: Error >> SD termination status: Error >> Termination: *** Backup Error *** >> >> Any idea what could be the cause of this ? >> > > Probably some limitation in the FD or SD how many attempts to write any > given data block are allowed. > > >> Could anyone check my director file to see if I haven't make any mistakes ? >> It's available on http://mordor.ath.cx/stuff/bacula-dir.conf.html >> > > I didn't check this... and I don't think the DIR conf is very important > here. If you suspect serious problems, use btape to verify your tape > drive setup, and do test runs of backup / restore / diff to verify the > overall correctness of your setup. > > Arno > > I already did the btape test twice, with success >> In advance thanks ! >> Julien >> >> >> Using Tomcat but need to do more? Need to support web services, security? >> Get stuff done quickly with pre-integrated technology to make your job easier >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >> _______________________________________________ >> Bacula-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> >> > > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
