>>>>> On Tue, 10 Jul 2007 09:10:24 -0600, Ken Gunderson said:
> 
> On Tue, 10 Jul 2007 11:12:35 +0100
> Martin Simmons <[EMAIL PROTECTED]> wrote:
> 
> > >>>>> On Mon, 9 Jul 2007 20:27:23 -0600, Ken Gunderson said:
> > > 
> > > Greetings:
> > > 
> > > Since my baffled post I've been doing some testing w/various sd.conf
> > > tweaks.  btape results and fbsd ports message initially recommended:
> > > 
> > > Due to lack of some features in the FreeBSD tape driver
> > > implementation you MUST add some OS dependent options to
> > > the bacula-sd.conf file:
> > > 
> > >   Hardware End of Medium = no;
> > >   Backward Space Record  = no;
> > >   Backward Space File    = no;
> > > 
> > > With 2 filemarks at EOT (see man mt):
> > >   Fast Forward Space File = no;
> > >   BSF at EOM = yes;
> > >   TWO EOF    = yes;
> > > 
> > > 
> > > While btape completes w/above no problem, from man mt it looks like FBSD
> > > supports bsr, however, and a few tests from command line seem to
> > > confirm so I trimmed sd.conf down thusly:
> > > 
> > >   Hardware End of Medium = no;
> > >   Fast Forward Space File = no;
> > >   BSF at EOM = yes;
> > >   TWO EOF = yes;
> > > 
> > > btape test completes fine and no longer recommend the bsr related
> > > tweaks.  Maybe they're not necessary and btape should be modified?
> > > Don't know about fill results yet - running now.  Hopefully I'll
> > > encounter the magic incantation to get my autochanger to actually
> > > change tapes...
> > 
> > In the current Bacula tape driver, Backward Space Record is only used to
> > verify that the last block has been written correctly when a tape gets full,
> > it is not strictly necessary.  In addition, the setting of Backward Space 
> > File
> > is ignored (bsf must work).
> > 
> > You might be able to use these settings on some FBSD tape drives:
> > 
> >   Fast Forward Space File = yes
> >   BSF at EOM = no
> >   TWO EOF = no
> > 
> > __Martin
> 
> Thanks. I know that it's optional and not needed.  But it seems btape's
> suggestions regarding sd.conf tweaks may be a bit inconsistent depending
> upon what flags are already set.
> 
> This is all a bit confusing on FBSD because per mtio man page various
> calls referenced in sd.conf docs are supported, e.g. mtiocget, mtbsr,
> mtfsf, etc.  Whether they're supported by SCSI device/driver remains
> uncertain, as I don't know how to test.  In this case I'm using LSI
> controller and mpt driver.  My assumption was that since btape said I
> needed sd flags such as Backward Space Record, etc. that it did not.
> But it looks like it does.  So I'm wondering whether the issue is with
> btape erroneously reporting or the mpt driver.
> 
> To recap, btape and manual backups and restores work but Autochanger is
> not changing tapes when it should so I suspected something was not
> quite right in sd.conf.

AFAIK, problems with the mechanics of tape changing in the autochanger will
not be affected by any of the mtio options.  The changer is a separate device
with its own protocol.

__Martin

-------------------------------------------------------------------------
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

Reply via email to