Re: autoflush and amstatus
On May 28, 2007, at 11:36 AM, James Brown wrote: Hi, After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I didn't want to run the 500GB backup again!). With autoflush enabled, will Amanda attempt to run another backup of the DLE that needs to be flushed? I am currently running 2.5.1p2. Thanks, JB The other piece you probably want to know is that even though it's dumping the DLE that is being flushed, the dump will be an incremental, not another full dump! Cheers, Bruce. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: autoflush and amstatus
E, 28 mai 2007 kirjutas James Brown <[EMAIL PROTECTED]>: After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I didn't want to run the 500GB backup again!). With autoflush enabled, will Amanda attempt to run another backup of the DLE that needs to be flushed? In my experience, yes. 'Autoflush' just means that as part of the amdump run, Amanda also tries to flush the contents of holding disk to tape. If an earlier dump of a particular DLE is on the holding disk and new amdump is run, that doesn't mean that this particular DLE doesn't get dumped. Why should it? Do you not want to have the up-to date backup of this DLE? At least on holding disk? I am currently running 2.5.1p2. Me too. -- Toomas Aas
Re: autoflush and amstatus
James Brown wrote: Hi, After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I didn't want to run the 500GB backup again!). With autoflush enabled, will Amanda attempt to run another backup of the DLE that needs to be flushed? Yes, amdump always do a dump of all dle. autoflush allow amdump to also flush to tape the dump that are already on holding disk. autoflush doesn't change what will be dumped. Jean-Louis
autoflush and amstatus
Hi, After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I didn't want to run the 500GB backup again!). With autoflush enabled, will Amanda attempt to run another backup of the DLE that needs to be flushed? I am currently running 2.5.1p2. Thanks, JB Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
Re: Amanda 2.5.2 bug report
A quick update. After generating about 15G of debug logs (chatty! :-) ), the issue hasn't yet recurred. I'm going to continue to beat on it to see if I can cause it to occur again. When and if that happens I'll assemble debug logs covering the crash. Hopefully, whatever was happening is now gone. Cheers, Bruce. On May 26, 2007, at 6:36 AM, Bruce Thompson wrote: Hi Jean-Louis, I'm giving that a try right now. Well, I tried it last night but awoke this morning to discover that I'd filling the /tmp partition and all h*ll was breaking loose with MailScanner! I hadn't realized just how verbose those debug logs would be (/tmp is only 1 gig). I'm going to give it a try with /tmp/amanda pointing to a much larger partition... Thanks for the help, Bruce. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: amanda-2.5.2
Try the attached patch, it remove the '-w10' flags because the irix od
doesn't accept it.
Jean-Louis
Jean-Francois Malouin wrote:
Not sure if this is relevant (first time I label a tape with
2.5.2-20070508 onward) but I got this from amlabel on a test server
running irix 6.5.57m compiled 64bit (CFLAG='-64 -mips4') with the
native sgi C compiler from the 2.5.2-20070523 snapshot:
# su amanda -c "/opt/amanda/spantest/sbin/amlabel spantest spantest-10 slot
10"
labeling tape in slot 10 (/hw/tape/tps6d4nrnsv):
rewinding, reading labelamlabel: Empty amanda header: buflen=32768 lsize=32768
Illegal option -- w
Usage: od [-bcdDfFhoOsSvxX] [file] [[+]offset[.][b]]
od [-v] [-A addr_base] [-j skip] [-N count] [-t type_str] ...
[file...]
amlabel: strange amanda header: ""
amlabel: Expected: "" Actual: "" , not an amanda tape
rewinding, writing label spantest-10, checking label, done.
regards,
jf
* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070524 09:26]:
Hello,
It's time for everyone to test the latest 2.5.2 snapshot before we
release 2.5.2p1.
Some bugs were found in amanda-2.5.2, most of them because of the new
IPv6 code and incompatibility with some platform:
* Many IPv6 bugs
o missing sockaddr_storage
o missing AI_V4MAPPED and AI_ALL
o compare of IPv4 and IPv6 v4mapped address.
o (bsd/bsdudp): server use two sockets, one for IPv4 and one
for IPv6
* amflush/autoflush
* chown/chmod
* amstatus
* compilation on some platform
* others small bugs
All of these bugs are fixed in the latest snapshot. We plan to release
amanda-2.5.2p1 next week.
I'm asking the help of all users to test it before we release 2.5.2p1,
don't wait the release to test it.
Latest snapshot can be found at http://www.zmanda.com/community-builds.php
Jean-Louis
diff -u -r --show-c-function --new-file --exclude-from=/home/martinea/src.orig/amanda.diff --ignore-matching-lines='$Id:' amanda-2.5.2/common-src/util.c amanda-2.5.2.popen/common-src/util.c
--- amanda-2.5.2/common-src/util.c 2007-05-23 08:06:36.0 -0400
+++ amanda-2.5.2.popen/common-src/util.c 2007-05-28 07:20:03.0 -0400
@@ -590,14 +590,14 @@ hexdump(
{
ssize_t rc = -1;
-FILE *stream = popen("od -w10 -c -x -", "w");
+FILE *stream = popen("od -c -x -", "w");
if (stream != NULL) {
fflush(stdout);
rc = (ssize_t)fwrite(buffer, len, 1, stream);
if (ferror(stream))
rc = -1;
- fclose(stream);
+ pclose(stream);
}
return rc;
}
Re: Amanda-2.5.2-20070523 amstatus
Try the attached patch.
Jean-Louis
McGraw, Robert P. wrote:
When I run amstatus --config daily --date"
zorn->[13] > amstatus --config daily --date
Using /var/amanda/daily/amdump from Fri May 25 07:51:23 EDT 2007
20070525075123 bers:/ 0
4649m finished (9:20:41)
20070525075123 bessel:/ 0
4621m finished (9:28:22)
20070525075123 bohr:/ 0
4967m finished (9:13:19)
:
taper writing, tapeq: 0
network free kps: 2090751
holding space : 8733m ( 2.13%)
chunker1 busy : 0:00:00 ( 0.00%)
chunker2 busy : 0:00:00 ( 0.00%)
chunker3 busy : 0:00:00 ( 0.00%)
chunker4 busy : 0:00:00 ( 0.00%)
chunker5 busy : 0:00:00 ( 0.00%)
chunker6 busy : 0:00:00 ( 0.00%)
chunker7 busy : 0:00:00 ( 0.00%)
chunker8 busy : 0:00:00 ( 0.00%)
chunker9 busy : 0:00:00 ( 0.00%)
dumper0 busy : 7:05:09 ( 87.98%)
dumper1 busy : 6:16:22 ( 77.88%)
dumper2 busy : 6:47:01 ( 84.22%)
My chunkers shows zero, but I have chunkers running.
My build is
zorn->[15] > amadmin daily version
build: VERSION="Amanda-2.5.2-20070523"
BUILT_DATE="Thu May 24 10:07:47 EDT 2007"
BUILT_MACH="SunOS zorn.math.purdue.edu 5.10 Generic_118833-03
sun4u sparc SUNW,Sun-Fire-280R"
Robert
_
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: [EMAIL PROTECTED]
Purdue University ROOM: MATH-807
Department of MathematicsPHONE: (765) 494-6055
150 N. University Street FAX: (419) 821-0540
West Lafayette, IN 47907-2067
diff -u -r --show-c-function --new-file --exclude-from=/home/martinea/src.orig/amanda.diff --ignore-matching-lines='$Id:' amanda-2.5.2/server-src/amstatus.pl.in amanda-2.5.2.amstatus.chunker/server-src/amstatus.pl.in
--- amanda-2.5.2/server-src/amstatus.pl.in 2007-05-23 08:04:53.0 -0400
+++ amanda-2.5.2.amstatus.chunker/server-src/amstatus.pl.in 2007-05-28 07:59:31.0 -0400
@@ -407,7 +407,7 @@ while() {
$serial=$4;
$serial{$serial}=$hostpart;
#$chunk_started{$hostpart}=1;
- #$chunk_time{$hostpart}=$1;
+ $chunk_time{$hostpart}=$1;
#$chunk_finished{$hostpart}=0;
$holding_file{$hostpart}=$5;
}
@@ -421,7 +421,7 @@ while() {
$serial=$4;
$serial{$serial}=$hostpart;
#$chunk_started{$hostpart}=1;
- #$chunk_time{$hostpart}=$1;
+ $chunk_time{$hostpart}=$1;
#$chunk_finished{$hostpart}=0;
$holding_file{$hostpart}=$5;
}
@@ -552,9 +552,9 @@ while() {
$hostpart=$serial{$serial};
$size{$hostpart}=$outputsize;
$dump_finished{$hostpart}=1;
- $busy_time{$2}+=($1-$dump_time{$hostpart});
+ $busy_time{$2}+=($1-$chunk_time{$hostpart});
$running_dumper{$2} = "0";
- $dump_time{$hostpart}=$1;
+ $chunk_time{$hostpart}=$1;
$error{$hostpart}="";
if ($3 eq "PARTIAL") {
$partial{$hostpart} = 1;
