Paul Bijnens wrote:
Are you very sure this was correctly copy/pasted? The lines
seem to be broken off.
True. I didn't paste correctly.
Another thing to explore is the fact you have over 100 entries for
that host.
Amanda communicates the estimates in one single udp dgram wich has
a payload a little less then 65535 bytes:
#define MAX_DGRAM (((1<<16)-1)-24-8)
My calculations do not come yet near that size, unless you have
ridiculous long directory names. Or you hit some other bug in sending
large UDP packets.
Actually you can find the dgram packet in one of the amandad.XXX.debug
files on the client. I guess the name is correct in that place?
It looks like:
=======
...
SERVICE sendsize
...
GNUTAR /the/am/name /the/dir/name 4 2004:5:19:22:6:8 1 OPTIONS
|;auth=bsd;compress-fast;index;exclude-list=/usr/lib/amanda/exclude.gtar;include-file=./blabla;
...
... (requesting each disklistentry)
...
amandad: time 222.547: sending REP packet:
----
Amanda 2.4 REP HANDLE 000-40B20608 SEQ 1085436125
OPTIONS features=fffffeff9ffe0f;
/dle/number/one 0 SIZE 5390
/dle/number/one 1 SIZE 10
... and so one...
======
Verify the request and reply line for that disk (just before/after too).
For a special disk /var/samba/projekte/Laufende/Klingelberg
the request line is
GNUTAR /var/samba/projekte/Laufende/klv 0 1970:1:1:0:0:0 -1 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/var/li
GNUTAR /var/samba/projekte/Laufende/klv 1 2004:5:17:22:29:55 -1 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/va
GNUTAR /var/samba/projekte/Laufende/Klingelnberg 0 1970:1:1:0:0:0 -1
OPTIONS |;bsd-auth;compress-fast;index;exclude-lis
GNUTAR /var/samba/projekte/Laufende/Klingelnberg 1 2004:5:13:21:42:31 -1
OPTIONS |;bsd-auth;compress-fast;index;exclude
GNUTAR /var/samba/projekte/Laufende/Kdh_BodyCare 0 1970:1:1:0:0:0 -1
OPTIONS |;bsd-auth;compress-fast;index;exclude-lis
GNUTAR /var/samba/projekte/Laufende/Kdh_BodyCare 1 2004:5:17:20:48:44 -1
OPTIONS |;bsd-auth;compress-fast;index;exclude
the reply line is
/var/samba/projekte/Laufende/Kazenmaier 0 SIZE 1070880
/var/samba/projekte/Laufende/Kazenmaier 1 SIZE 220
/var/samba/projekte/Laufende/Kdh_BodyCare 0 SIZE 5940
/var/samba/projekte/Laufende/Kdh_BodyCare 1 SIZE 20
/var/samba/projekte/Laufende/Klingelnberg 0 SIZE 45620
/var/samba/projekte/Laufende/Klingelnberg 1 SIZE 60
/var/samba/projekte/Laufende/klv 0 SIZE 104210
/var/samba/projekte/Laufende/klv 1 SIZE 26030
When server receives the reply packet with the estimates,
you can see in amdump.1 the result like:
planner: time 80.851: got result for host neptun disk /: 0 -> 457710K, 1
-> 2980K, -1 -> -1K
Is the name now mangled to "projojeke"?
The mangled name I found in log.20040525.0 but not in amdump.1
In amdump.1 everything looks OK.
planner: time 0.627: setting up estimates for
neptun:/var/samba/projekte/Laufende/Klingelnberg
neptun:/var/samba/projekte/Laufende/Klingelnberg overdue 5 days for level 0
setup_estimate: neptun:/var/samba/projekte/Laufende/Klingelnberg:
command 0, options:
last_level 1 next_level0 -5 level_days 3
getting estimates 0 (45620) 1 (60) -1 (-1)
You get the "badly formatted response from" error when one of these
things happen:
- The datagram line could not be parsed by
(sscanf(t - 1, "%d SIZE %ld", &level, &size) != 2)
- The estimate was for a level that was not requested
Which one would it be?
Level 0 should it be.
Parsing should be possible.
Thanks Stefan
|