Hi Ralf, On Thursday 26 April 2007 writes Ralf: > Falk Sauer <falk <at> hb-fein.de> writes: > > Hi Ralf, > > > > On Tuesday 24 April 2007 writes Ralf: > > > we are using Bacula 2.0.2 on Suse Linux with the Tandberg tape drive > > > DLT-V4 and DLTtape VS1 cartridges. Unfortunately it´s not clear to me > > > which "media type" I should use to have the highest effort. Concerning > > > the manual the cartridge can hold 160G uncompressed / 320G compressed > > > on DLT-V4 drives but the cartridge is always marked full at approx. > > > 35G. > > > > > > Which media type should I use? > > > > The media-type statement in conf is afair only a description/name for > > same medium-types/class. > > If you have a DLT-VS1 Tape medium, name the media type DLT-VS1 and your > > V4 name can DLT-V4. This is only a Name for _same_ media types thats > > going on a (one or more) special Storage. If you use 2 media types in one > > Tape drive use one media-type for them. Media Type has imho no side > > effects to any max volume size params. That's all you can also find in > > the documentation. > > > > Your Problem has imho a other cause. Have you defined any Volume size? > > remove it for testing. > > Have you initially rewinded your tape and a > > mt weof -f /dev/nst0 > > making before you labeled the medium? > > Have you a new Tape for testing or a old one, often used with errors? > > Can you write more uncompressed bytes with tar or cpio to this tape? > > > > regards > > Falk > > Hi Falk, > > thanks for your reply. > > I´ve always use new sealed cartridges of Tandberg. But in the initial setup > process I have not rewind the mediums with "mt weof -f /dev/nst0". Is this > also necassary with new cartridges? > > Here an example of my problem: > A weekly marked cartridge was full at 6GB. I have delete the catalog in > Bacula and after I delete the content of the cartridge with the command "mt > -f /dev/st0 erase". Then I label the medium in Bacula again and wrote data > to it. Now the cartridge is market full at 12,5GB. Perhaps I have a lack of > tape geometry?
please test your drive with tar or cpio, make a verify and look how much bytes to fit into the tape, use real data for them not /dev/zero. It's sounds to me like a defective drive or a bad cabeling or anything else between drive and os. Bacula read an eof from your drive, you must clarify it's a problem in the complex drive, controller, os or it's a problem in the interaction between bacula and the os with this special drive type. regards Falk ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
