* Jean-Francois Malouin <Jean-Francois.Malouin AT bic.mni.mcgill DOT ca> 
[20081110 12:27]:
> Hello,
> 
> I've finally got to install amanda-2.6.0p2 on a system going soon into
> production and while getting used to the new features and I noticed a
> few things that have changed since 2.5.x :

Since no-one is answering, I'll continue my lonely tirade :)

What happened to the `CONFIGURE_COMMAND' line in the amandad debug files?

This is very useful when testing different config setups. For
instance, it took me a while to discover that I had made a typo while
running configure with `--with-maxtapeblocksize'. I would had spotted
this right away with that line in the amandad debug file. After a lot
of greping through the log files I discovered, buried in the taper
debug files, the only place afaik where one can find the tapetype
blocksize numerical value in lines like:

<timestamp>: taper: Building type 3 (FILE) header of size 2097152 using:

cheers,
jf

> 
> - I use amtoc after a dump ends to get stats on what was written on
> tape and noticed that it doesn't parse correctly the log files and the
> toc files end up not showing what was written on tape. Looking at the
> source I believe that this is due to the fact that amtoc doesn't parse
> lines that start with 'PART' as the new log format seems to use
> compared to 'CHUNK' in pre-2.6.x.
> 
> - amstatus doesn't show which tape(s) is being used and how much data
> been written to it so far, a useful feature when I want to check that
> a flush is being done correctly when using a changer with 'runtapes>1'
> 
> - As I posted a few days ago, amreport doesn't report correctly the
> aggragated transfer rate to tape beyond 99.99MiBs...
> 
> - The new version features 'device_output_buffer_size' that replaces
> 'tapebufs'. Any hint on a ballpark figure for this? Right now I have
> set it to 8192k (I use a blocksize=2048k) but I really don't know if I
> overshooting with this...the server has 32GB of memory btw.
> 
> Thank you for the amazing work you guys are doing!
> jf
> -- 
> <° >< Jean-François Malouin          McConnell Brain Imaging Centre        
> System/Network Administrator        Montréal Neurological Institute
> 3801 Rue University, Suite WB219, Montréal, Québec, H3A 2B4, Canada

-- 
<° >< Jean-François Malouin          McConnell Brain Imaging Centre        
System/Network Administrator        Montréal Neurological Institute
3801 Rue University, Suite WB219, Montréal, Québec, H3A 2B4, Canada