Hi, I'll copy this to the list again.
On 9/2/2006 2:58 PM, Frederik wrote: > On 9/1/06, Arno Lehmann <[EMAIL PROTECTED]> wrote: > >> Hello, >> >> On 9/1/2006 3:26 PM, Frederik wrote: >> > Hi, could the following messages be a sign of a bad tape, or would >> > this have another cause? >> >> Yes. >> ;-) >> >> > 01-Sep 03:05 server-sd: Recycled volume "donderdag" on device "tape" >> > (/dev/st0), all previous data lost. >> > 01-Sep 05:19 server-sd: End of Volume "donderdag" at 3:6763 on device >> > "tape" (/dev/st0). Write of 64512 bytes got -1. >> > 01-Sep 05:19 server-sd: Re-read of last block succeeded. >> > 01-Sep 05:19 server-sd: End of medium on Volume "donderdag" >> > Bytes=3,436,102,519 Blocks=53,263 at 01-Sep-2006 05:19. >> > 01-Sep 05:20 server-sd: Job FullBackup.2006-08-31_22.05.00 waiting. >> > Cannot find any appendable volumes. >> >> You'd need to be a little more specifc. The message only shows a tape >> filling and Bacula requesting the next one. >> >> Obviously, without more information about how much data you usually put >> onto that type of tape it's hard to tell if this is a problem. Bacula, >> at least, didn't detect any problems. > > > OK, that was another option... I'm not sure what kind of tape was in > the drive, as I'm not on site. This is the kind of drive which is > being used: > > Vendor: HP Model: C1537A Rev: L411 > Type: Sequential-Access ANSI SCSI revision: 02 > (should be DDS-3) > > The amount of data to backup is about 5GB and backups on other tapes > go fine. So I suspected that either: > - this one tape has a smaller capacity than others, which makes that > only this backup fails because of lack of space > - the tape is damaged, and bacula stops writing after 3,5 GB of data. In that case you'd _often_ see some messages to the effect that the WEOF failed or the last block could not be read correctly. Not always, though. > > But if I'm correclty reading, you don't think that the second case is > possible, which indeed would mean that there's one tape being used > which is too small. Sounds reasonable, but it might also be that you've got lots of already-compressed data going on the tape where hardware compression is enabled. This ususally leads to a decrease in effective tape caacity. Provided you've got shell access to the machine in question you could check the tape type by using tapeinfo or mt status commands, by the way. Arno > Thanks, -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- 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 Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
