Amanda-Users

Re: amtapetype - silly thing I tried

2007-06-01 13:47:15
Subject: Re: amtapetype - silly thing I tried
From: Jon LaBadie <jon AT jgcomp DOT com>
To: amanda-users AT amanda DOT org
Date: Fri, 1 Jun 2007 13:35:56 -0400
On Fri, Jun 01, 2007 at 12:49:32PM -0400, Chris Hoogendyk wrote:
> 
> 
> Dustin J. Mitchell wrote:
> > On Fri, Jun 01, 2007 at 10:40:38AM -0400, Jon LaBadie wrote:
> >   
> >> On Fri, Jun 01, 2007 at 08:00:21AM -0400, Jean-Louis Martineau wrote:
> >>     
> >>> Jon,
> >>>
> >>> amtapetype should terminate once it fill the disk.
> >>>
> >>> Jean-Louis
> >>>       
> >> I didn't see any smiley there ;) so I'll just note that once
> >> amtapetype seemed to recognize the file driver I half-expected
> >> it to also see the EOF like taper does.
> >>     
> >
> > If I understand correctly (and just to summarize), Jon, you expected
> > amtapetype to terminate when the tape was filled to its stated capacity
> > (stated in the tapetype definition..) the way taper does.  Instead,
> > amtapetype runs until the OS returns ENOSPC ("No space available") and
> > then terminates, probably with a pretty accurate description of the
> > amount of space available on the partition.
> >
> > Sound about right?
> >   

Dustin,

"Expected" is not quite descriptive.  I was first surprised to see
that amtapetype even used the file driver semantics.  Once it did,
I was then curious, and yes, mildly surprised, that it did not
honor the tapetype definition.

> 
> Just an added comment: amtapetype is a diagnostic tool. It is hammering
> the device trying to determine what its limits are. It doesn't want a
> configuration file to tell it some limit that might not be right. It's
> going to figure it out for itself. The interesting thing here might be
> getting the performance of your drive, even though you are setting a
> lower limit for how much drive space you ultimately want amanda to use.
> 

Chris,

While amtapetype was running those were exactly my thoughts.  That it
probably should go until the FS was full, but that if it did not, and
stopped at the tapetype definition, then the performance info would
indeed be useful.  If one wanted a system-derived, rather than file:
driver-drived capacity value, then one could simply set the tapetype
definition to a monster number.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)

<Prev in Thread] Current Thread [Next in Thread>