From the debug file:
sendbackup: time 2612.878: 62:size(|): DUMP: 17753400 blocks
(17337.30MB)
amanda parse the number of block but it think they are blocks of 512 bytes.
This problem is fixed only in amanda-2.5.2b1 (The MB value is used).
Jean-Louis
Sebastian Henrich wrote:
My OS
Because most user use tar on linux, and it's new that the blocksize is 1024.
You can change client-src/sendbackup-dump.c:
AM_SIZE_RE(DUMP: [0-9][0-9]* blocks, 512)
to
AM_SIZE_RE(DUMP: [0-9][0-9]* blocks, 1024)
I also fixed the bug in the latest 2.5.1p3 snapshot available from
At 16:40 16.04.2007, Jean-Louis Martineau wrote:
Because most user use tar on linux, and it's new that the blocksize is 1024.
This makes sense. What are the disadvantages of a tar backup?
You can change client-src/sendbackup-dump.c:
AM_SIZE_RE(DUMP: [0-9][0-9]* blocks, 512)
to
Here is the result after deleting full-comp und incr-comp.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
--
My OS is openSUSE 10.1.
server:~ # tar --version
tar (GNU tar) 1.15.1
server:~ # dump
dump 0.4b41 (using libext2fs 1.38 of 30-Jun-2005)
The last dendbackup.*.debug is attached.
Thanks
Sebastian
At 13:50 13.04.2007, Jean-Louis Martineau wrote:
The orig-kb is the size reported by the
Hello again,
I still try find the cause of my problems with amanda. When the
backup finishes, I get the following dump summary:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
Post the amdump.1 log file.
Jean-Louis
Sebastian Henrich wrote:
Hello again,
I still try find the cause of my problems with amanda. When the backup
finishes, I get the following dump summary:
DUMPER STATSTAPER STATS
HOSTNAME DISK
