On Fri, Jun 02, 2006 at 06:25:11PM -0400, Jon LaBadie wrote:
> On Fri, Jun 02, 2006 at 11:10:10PM +0200, Paul Bijnens wrote:
> > >
> > >In my gnutar-lists directory, all the files are named
> > >"xxx.new".  Looking at an abandoned installation on
> > >another server, most of the files have the ".new"
> > >stripped off.  How should the files appear?
> > 
> > There shouldn't be .new files when the run is finished.
> > Maybe you have permission problems on the files,
> > resulting in not being able to "mv" the .new file?
> > 
> 
> That is good to know, I never looked at the gnutar-list
> directory before.  But I considered permissions.  Look
> alright to me:
> 
> $ ls -la
> total 3728
> drwxr-xr-x   2 amandabackup disk    4096 Jun  2 04:37 .
> drwxr-xr-x  20 amandabackup disk    4096 May 26 15:20 ..
     <snip>
> -rw-------   1 amandabackup disk 1615513 Jun  1 05:42 bigcowUSR_0.new
> -rw-------   1 amandabackup disk 1615513 Jun  2 05:42 bigcowUSR_1.new
> 
...
> 
> Could the lack of any files without the ".new" be a reason
> why my incrementals are actually full dumps?
> 

Following up to my own reply:

I checked the most recent debug files and they show the "*.new" files
are being used.  For example, corresponding to the last listing above,
two lines from sendbackup...debug:

sendbackup-gnutar: time 0.207: doing level 1 dump as listed-incremental \
  to /var/lib/amanda/gnutar-lists/bigcowUSR_1.new

sendbackup: argument list: gtar --create --file - --directory /usr \
  --one-file-system \
  --listed-incremental /var/lib/amanda/gnutar-lists/bigcowUSR_1.new \
  --sparse --ignore-failed-read --totals \
  --exclude-from /tmp/amanda/sendbackup.USR.20060602043755.exclude .


-- 
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)