On Tue, Jan 5, 2010 at 3:00 PM, Phil Stracchino <alaric AT metrocast DOT net> 
wrote:
> Brian Debelius wrote:
>> I'm not seeing anywhere close to 60M/s ( < 30 ).  I think I just fixed
>> that.  I increased the block size to 1M, and that seemed to really
>> increase the throughput, in the test I just did.  I will see tomorrow,
>> when it all runs.
>
> Yes, if you aren't already, whenever writing to tape you should almost
> without exception (and certainly on any modern tape drive) be using the
> largest block size that btape says your drive supports.
>

I tried to do that years ago but I believe this made all tapes that
were already written to unreadable (and I now have 80) so I gave this
up. With my 5+ year old dual processor Opteron 248 server I get 25MB/s
to 45MB/s despools (which measures the actual tape rate) for my LTO2
drives. The reason for the wide range seems to be compression.

John

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users