On Fri, Apr 10, 2009 at 1:54 PM, Gene Heskett <gene.heskett AT verizon DOT net> 
wrote:
> Dustin;  It is looking like its catching up, after several runs with
> intervening versions, it has caught up with whatever change made that made it
> think everything was new.  I don't believe it was device major/minors that did
> it, since when the first time I ran the 0331 version it was a total failure,
> not 'to big' failures like I have had with 0321 & newer till its caught up
> again.  Reverting to 0319 from 0331 made it run normal.  But every newer
> version has acted like the device mapper had moved all the disks around, and
> the option --no-device-check was being ignored.  So I have NDI what the real
> problem is/was.  I am continuing to build & test, 0327 is building now.

As in the past, this problem really exists between tar and the kernel,
so Amanda versions aren't relevant.  The one thing that you can check
for us (as opposed to for the kernel or tar developers) is that Amanda
is properly sending the --no-device-check to tar.  You should see this
either in your sendbackup debug logs or your runtar debug logs.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com