Re: amanda-2.6.0p2: a few remarks and questions
2008-11-12 10:25:45
* Jean-Louis Martineau <martineau AT zmanda DOT com> [20081111 20:12]:
> Hi Jean-François,
>
> Can you try the attached patch?
Tried it but something is still missing. Mind you, I just applied
the patch and recompiled: this is from a previous run.
-amreport: patch works: it reports tape rate above 100MBs
Avg Tp Write Rate (k/s) 109575 109575 --
-amstatus: I still don't get the lines 'tape X', like:
taped : 25 422328m 423178m ( 99.80%) ( 99.80%)
tape 1 : 25 422328m 423178m (109.40%) av24_U00061L3 (79 chunks)
-amtoc: I was doing my own edit of the amtoc perl script when you sent
me the patch. If I run the patched amtoc on a previous log file I get
something like:
# Server:/partition date lev size[Kb]
0 av48-1_top_R00012L4: 200811101 - -
1 gustav:/raid/prefrontal 200811101 0 *16777216
2 gustav:/raid/prefrontal 200811101 0 *16777216
...
21 gustav:/raid/prefrontal 200811101 0 *16777216
22 gustav:/raid/prefrontal 200811101 0 367489930
Notice the '*'. There is something wrong around line 228 of amtoc:
if(!/^CHUNK/){
# this case should never happend:
$strange=1;
$note = "*";
}
It inserts the '*' on the chunk size. Also the total:on_tape is missing.
This is simple perl stuff, I should be able to do something about it!
Thanks a lot.
jf
>
> Jean-Louis
>
> Jean-Francois Malouin wrote:
> >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 :
> >
> >- 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
|
|
|