Re: 3.2.0svn3411
What's your flush-threshold setting? amgetconf CONF flush-threshold-scheduled amgetconf CONF flush-threshold-dumped amgetconf CONF taperflush Stefan G. Weichinger wrote: Am 21.09.2010 00:09, schrieb Jean-Louis Martineau: Can you provide the complete amflush.1 or amdump.1 files attached. Stefan
Re: 3.2.0svn3411
Am 21.09.2010 00:09, schrieb Jean-Louis Martineau: Can you provide the complete amflush.1 or amdump.1 files attached. Stefan jlm.tgz Description: application/compressed-tar
Re: 3.2.0svn3411
On Mon, Sep 20, 2010 at 11:20 PM, gene heskett ghesk...@wdtv.com wrote: with taper_debug 9 I had a 174 meg taper log, which still didn't make any sense as it was reporting about 6 lines for every 32k write, so I dropped it to 2. I grepped for the differences in the man tree but didn't see anything about the verbosity diffs. So now it's writing to tape. So the problem is solved. Does it not write to tape with a lower debug level? Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: Nitpick - amreport statistics
On Mon, Sep 20, 2010 at 6:56 PM, Jon LaBadie j...@jgcomp.com wrote: Looks better to my eye. Any one else? With Jean-Louis' review, committed in r3428. Thanks! Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.2.0svn3411
On Tuesday, September 21, 2010 11:34:54 am Dustin J. Mitchell did opine: On Mon, Sep 20, 2010 at 11:20 PM, gene heskett ghesk...@wdtv.com wrote: with taper_debug 9 I had a 174 meg taper log, which still didn't make any sense as it was reporting about 6 lines for every 32k write, so I dropped it to 2. I grepped for the differences in the man tree but didn't see anything about the verbosity diffs. So now it's writing to tape. So the problem is solved. Does it not write to tape with a lower debug level? Dustin No, it ceases to write to the 'tape' after 3402, I think. Yes, 3402 worked, 3411 failed. See my previous reply where the 3 amgetconf lines were asked about. I read ChangeLogs, and this is the first I'd heard of those 3 new variables. This stuff belongs in the ChangeLog! With a line saying new amanda.conf vars, listing them comma separated. That would have been trigger enough to go read the man page. dumps has been moved to a much larger playground, and 3427 installed just to check my theory that zero detection is thwarted by a holding disk smaller than the vtape. Ergo no flush by taper. Even when amflush is called by hand. Also, a separate squawk, starting at about svn3388 I think, the emailed report is suddenly being spammed by a hundred lines or so of stuff about in- accessible sockets and such in /home/gene/tmp, which contains other stuff I would rather were included in the backups. But that's a different problem. Sorry if I come across a bit grouchy, I've been taking antibiotics for a strep throat the last few days. And I'm about worn out trying to get this place put back together for the winter after a 112 mph wind came through the neighborhood on June 24th, demolishing or uprooting most of the trees. We lost 3 of 4 40 year old pines, the roof, parts of the back porch and all the privacy fencing. Amazingly a 60 foot pin oak in the front yard stood. The replacement fencing I built post hole by post hole and screw by screw, and it can be seen at http://gene.homelinux.net:85/gene/fence I'll be 76 in another few days, and folks keep telling me I should retire. I keep trying to, but such as this gets in the way... The bottom of my fishing boat hasn't been wet since summer 2009. And right now I am working on its shed, which although tattered, didn't blow away in the wind as it was below the house on the lee side. Pix in the camera I'll put up when I'm done with that. I used to have a life, but its about used up I think. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Your happiness is intertwined with your outlook on life.
Re: 3.2.0svn3411
gene heskett wrote: Butting in here, but a nice bright light bulb just came on. I get a big fat 0 for all three amgetconf's above. Izzat my problem? [r...@coyote amanda]# amgetconf Daily flush-threshold-scheduled 0 [r...@coyote amanda]# amgetconf Daily flush-threshold-dumped 0 [r...@coyote amanda]# amgetconf Daily taperflush 0 A value of 0 is good, amanda should try to flush everything. Jean-Louis
Re: 3.2.0svn3411
Gene, this is counterproductive at this point. You've named a few things that seem to be wrong, all of which are unrelated. You've changed things between each email, and claimed a number of different symptoms. PLEASE: slow down. Find *one* failure, describe it fully, and track it down to its cause, using logfiles if possible. Be as methodical as possible. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.2.0svn3411
I can't find why it flush nothing. Can you upgrade to latest SVN and try the attached patch, it add mode degugging. Add 'debug-driver 1' in amanda.conf Retry amflush and send me the resulting amflush.1 file. Jean-Louis Stefan G. Weichinger wrote: Am 21.09.2010 00:09, schrieb Jean-Louis Martineau: Can you provide the complete amflush.1 or amdump.1 files attached. Stefan
Re: 3.2.0svn3411
Attachment included.
Jean-Louis
Jean-Louis Martineau wrote:
I can't find why it flush nothing.
Can you upgrade to latest SVN and try the attached patch, it add mode
degugging.
Add 'debug-driver 1' in amanda.conf
Retry amflush and send me the resulting amflush.1 file.
Jean-Louis
Stefan G. Weichinger wrote:
Am 21.09.2010 00:09, schrieb Jean-Louis Martineau:
Can you provide the complete amflush.1 or amdump.1 files
attached.
Stefan
diff --git a/server-src/driver.c b/server-src/driver.c
index 6182ee0..ea66006 100644
--- a/server-src/driver.c
+++ b/server-src/driver.c
@@ -3735,18 +3735,30 @@ tape_action(
}
}
if (nb_taper_active = 1) {
-my_flush_threshold_dumped = flush_threshold_dumped +
-(nb_taper_active-nb_taper_active) * tape_length;
-my_flush_threshold_scheduled = flush_threshold_scheduled +
- (nb_taper_active-nb_taper_active) * tape_length;
-my_taperflush = taperflush + (nb_taper_active-nb_taper_active) * tape_length;
+ my_flush_threshold_dumped = flush_threshold_dumped;
+ my_flush_threshold_scheduled = flush_threshold_scheduled;
+ my_taperflush = taperflush;
} else {
-my_flush_threshold_dumped = flush_threshold_dumped +
-nb_taper_active * tape_length;
-my_flush_threshold_scheduled = flush_threshold_scheduled +
- nb_taper_active * tape_length;
-my_taperflush = taperflush + nb_taper_active * tape_length;
-}
+ my_flush_threshold_dumped = flush_threshold_dumped +
+nb_taper_active * tape_length;
+ my_flush_threshold_scheduled = flush_threshold_scheduled +
+ nb_taper_active * tape_length;
+ my_taperflush = taperflush + nb_taper_active * tape_length;
+}
+
+driver_debug(1, _(nb_taper_active: %d\n), nb_taper_active);
+driver_debug(1, _(my_flush_threshold_dumped: %lld\n), (long long)my_flush_threshold_dumped);
+driver_debug(1, _(my_flush_threshold_scheduled: %lld\n), (long long)my_flush_threshold_scheduled);
+driver_debug(1, _(my_taperflush: %lld\n), (long long)my_taperflush);
+driver_debug(1, _(taper state: %d\n), taper-state);
+driver_debug(1, _(taper_nb_scan_volume state: %d\n), taper_nb_scan_volume);
+driver_debug(1, _(degraded_mode: %d\n), degraded_mode);
+driver_debug(1, _(runq: %d\n), empty(runq));
+driver_debug(1, _(directq: %d\n), empty(directq));
+driver_debug(1, _(roomq: %d\n), empty(roomq));
+driver_debug(1, _(idle_reason: %d\n), idle_reason);
+driver_debug(1, _(degraded_mode: %d\n), degraded_mode);
+driver_debug(1, _(force_flush: %d\n), force_flush);
// Changing conditionals can produce a driver hang, take care.
//
Re: Nitpicks?
On Tue, Sep 21, 2010 at 1:26 PM, Chris Nighswonger cnighswon...@foundations.edu wrote: This may be a little late, but it would be nice to have a switch on most status, etc. utils to format the output for texting to a mobile device rather than email. Almost the exact same thing was requested earlier by Douglas K. Rand. There are a number of suggestions to change the way notifications are done in Amanda. And from experience, if those are implemented, it will generate an even larger number of requests (HTML emails, mobile-friendly HTML emails, Growl notifications, ..). As I mentioned earlier, I think the better approach is to design a generic notification interface into Amanda, and let other applications do the required formatting/filtering. That said, I wouldn't object to a patch to amcheck to generate pages in the case of an error. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: Nitpicks?
On 9/21/10 2:42 PM, Dustin J. Mitchell wrote: On Tue, Sep 21, 2010 at 1:26 PM, Chris Nighswonger cnighswon...@foundations.edu wrote: This may be a little late, but it would be nice to have a switch on most status, etc. utils to format the output for texting to a mobile device rather than email. Almost the exact same thing was requested earlier by Douglas K. Rand. There are a number of suggestions to change the way notifications are done in Amanda. And from experience, if those are implemented, it will generate an even larger number of requests (HTML emails, mobile-friendly HTML emails, Growl notifications, ..). As I mentioned earlier, I think the better approach is to design a generic notification interface into Amanda, and let other applications do the required formatting/filtering. That said, I wouldn't object to a patch to amcheck to generate pages in the case of an error. Perhaps some sort of structured output with style sheets for selection of detail or urgency level and formatting? Might even be something off the shelf that could be used/adapted. Then just about anyone could create their own style sheet. -- --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst hoogen...@bio.umass.edu --- Erdös 4
Re: Nitpicks?
This may be a little late, but it would be nice to have a switch on most status, etc. utils to format the output for texting to a mobile device rather than email. According to Verizon's website, the 160 char limit on text messages is as follows: The 160 character limit includes the sender's email address (if applicable), the composed message and, if provided, the subject and callback number. It seems that sending an email to a device that only supports text messages results in char-length-of-email/160 text messages. This can add up if one has to pay per message or has a set limit of free messages. Output formatted for texting might be sent only when there was an error detected or might only include limited summary info depending on the script being run. Kind Regards, Chris On Thu, Sep 9, 2010 at 11:55 AM, Dustin J. Mitchell dus...@zmanda.com wrote: I bet most of you have some small nitpick with Amanda that you've never felt warranted an email. Well, now's your chance! I'd like to put some polish on Amanda, and it's hard for me to see the areas that need burnishing, since I work on Amanda all day, every day. - typo in a manpage? - command-line usage oddity? - confusing use of terminology? - something else? Start up a new thread on the mailing list, or email me privately if you'd prefer, to let me know what's bugging you. Bonus points for also supplying a patch, but that's not at all required! Note that I do reserve the right to say, actually, that's complicated (and explain why). Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: My 3.1.2 server starts ok, but taper never writes anything
On Mon, Sep 20, 2010 at 3:21 PM, Dustin J. Mitchell dus...@zmanda.com wrote: It's impractical to run this check in ./configure, but what do you think about running this check even on 'make all'? I committed this - on FreeBSD, this test will occur on 'make install'. Do you mind adding a FreeBSD problem report, if there's not one already? Can you give me a pointer so I can add myself as cc? This would still be great.. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.2.0svn3411
On Tuesday, September 21, 2010 10:20:53 pm Dustin J. Mitchell did opine: Gene, this is counterproductive at this point. You've named a few things that seem to be wrong, all of which are unrelated. You've changed things between each email, and claimed a number of different symptoms. Only 2 come to mind and the one listed below is the primary one. PLEASE: slow down. Find *one* failure, describe it fully, and track it down to its cause, using logfiles if possible. Be as methodical as possible. Dustin One failure? Nothing later than 3402 will write from the holding disk to the tape. The taper.*.debug log shrinks from 16 or 17k to 794 bytes, and that is the one you have already. From 3411 on, I cannot flush whats in the holding disk even when running amflush by hand, amflush exits about 2 or 3 seconds after tapping the drive with one read, and one small write, probably the status file, and without any further data being added to the taper.debug file. I have 3427 installed for tonights run, with two changes, taper_debug is now set to 2 as 9 made a 170+ megabyte taper.*.debug file last night, and dumps has moved to a partition with 600Gb more space. Tonight's run will test my theory. If it fails, then I back up to 3402 see if I can flush it by hand. I know I can with 3341. More after the run. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale.
