On Friday 10 April 2009, Paul Yeatman wrote:
>On Fri, 2009-04-10 at 15:26 -0400, Gene Heskett wrote:
>> On Friday 10 April 2009, Dustin J. Mitchell wrote:
>> >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.
>>
>> You recall that when I went from 0319 to 0331, it wasn't this, it was a
>> total, all results missing failure, and reverting to 0319 fixed that, so I
>> believe I am looking at 2 distinct problems.
>>
>> >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
>>
>> I can see it in the htop report while its actively running, but haven't
>> looked at the runtar debug logs yet, hang on.  Mummmmmmm, no runtar logs.
>> I am running amgtar.
>>
>> From the htop screen: No, I can't show it, amgtar has finished all DLE's
>> for this run, and the printer just spit out a normal report.
>>
>> I just grepped all the amgtar.*.debug files, and it is not noted in any of
>> them.  This begins to quack like amgtar is ignoring that option?  Please
>> say it isn't so...  If so, it seems like it should log that the option
>> wasn't done, somehow.
>
>If I'm following at all, for amgtar, you should be setting this as a
>property field in your amgtar application section (in my case "yes")
>
>        property "CHECK-DEVICE" "yes"
>
>and it should be showing up in the amgtar.*.debug log as
>
>1239319047.814503: amgtar: CHECK-DEVICE yes
>
Oh its in amgtar.*.debug alright, as CHECK-DEVICE yes.  This is NOT what it 
has been ordered to do.  Since the debug is small, I'll include it:

1239390447.316901: amgtar: pid 24248 ruid 500 euid 500 version 2.6.2alpha: 
start at Fri Apr 10 15:07:27 2009
1239390447.316955: amgtar: version 2.6.2alpha-20090327
1239390447.317069: amgtar: GNUTAR-PATH /bin/tar
1239390447.317075: amgtar: GNUTAR-LISTDIR /usr/local/var/amanda/gnutar-lists
1239390447.317079: amgtar: ONE-FILE-SYSTEM yes
1239390447.317083: amgtar: SPARSE yes
1239390447.317087: amgtar: NO-UNQUOTE no
1239390447.317091: amgtar: ATIME-PRESERVE yes
1239390447.317095: amgtar: CHECK-DEVICE yes <-----------------------
1239390447.317098: amgtar: SIZE ^ *Total bytes written: [0-9][0-9]*
1239390447.317103: amgtar: IGNORE : Directory is new$
1239390447.317106: amgtar: IGNORE : Directory has been renamed
1239390447.317110: amgtar: NORMAL ^could not open conf file
1239390447.317114: amgtar: NORMAL ^Elapsed time:
1239390447.317118: amgtar: NORMAL ^Throughput
1239390447.317122: amgtar: NORMAL : socket ignored$
1239390447.317127: amgtar: NORMAL : File .* shrunk by [0-9][0-9]* bytes, 
padding with zeros
1239390447.317131: amgtar: NORMAL : Cannot add file .*: No such file or 
directory$
1239390447.317135: amgtar: NORMAL : Error exit delayed from previous errors

But, from my amanda.conf:

define application-tool app_amgtar {
     comment "amgtar"
     plugin  "amgtar"
     #property "GNUTAR-PATH" "/path/to/gtar"
     #property "GNUTAR-LISTDIR" "/path/to/gnutar_list_dir"
     #default from gnutar_list_dir setting in amanda-client.conf
     #property "ONE-FILE-SYSTEM" "yes"  #use '--one-file-system' option
     #property "SPARSE" "yes"           #use '--sparse' option
     #property "ATIME-PRESERVE" "yes"   #use '--atime-preserve=system' option
     property "CHECK-DEVICE" "no"       #use '--no-check-device' if set to "no"
}

I wasn't looking in amgtar for the right string obviously.  Duh.  And here is 
part of the problem.  Is my syntax correct in the .conf snippet above?

-- 
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)
Matz's Law:
        A conclusion is the place where you got tired of thinking.