Loki Harfagr schreef:
> Le Sun, 18 Sep 2005 14:24:04 +0200, jacq a écrit :
>
>
>>Giovanni schreef:
>>
>>>On 09/18/05 12:01, jacq wrote:
>>>
>>>
>>>>Hello,
>>>>
>>>>Does anyone have a clue why [--verify] does work on Slackware 10.0
>>>>(tar-1.14-i486-4) but NOT on Slackware 10.1 (tar-1.15.1-i486-1)?
>>>>Or has tar [--verify] problems with RAID?
>>>>My Slackware 10.0 runs on a simple system with /dev/hda EXT3 disks.
>>>>My Slackware 10.1 runs on a system with RAID5 and RAID1 and EXT3
>>>>and ReiserFS filesystems ....
>>>>
>>>>example:
>>>>
>>>>$ tar cvf /usr/backups/username/backup.tar /home/username/* --verify
>>>>
>>>>tar: --verify: Cannot stat: No such file or directory
>>>>tar: Error exit delayed from previous errors
>>>>
>>>>
>>>
>>>I had the same problen with the --totals or --exclude options. It
>>>appears that from version 1.5 tar does not accepts anymore the options
>>>after filename/pathame. Previous versions did not accept the other way.
>>>I had to modify all my backup scripts.
>>>
>>>try:
>>>$ tar cvf /usr/backups/username/backup.tar --verify /home/username/*
>>>
>>>Ciao
>>>Giovanni
>>
>>
>>More bad news!
>>--------------
>>
>>$ tar cvf /usr/backups/username/backup.tar --verify /home/username/*
>>(or $ tar cvP --verify -f /usr/backups/username/backup.tar
>>/home/username/*tar)
>>
>>both don't produce errors anymore, but
>>--verify, --compare, --diff, -d or -W just don't work!
>>
>>I tried this:
>>
>>$ tar cvf /usr/backups/username/backup.tar --verify /home/username/* |more
>>
>>output on screen something like this:
>>
>>$ filename1
>>$ filename2
>>$ filename3
>>etc.
>>[more]
>
>
> Note: If you are in a hurry, jump directly to mark (*URGENTMODE*)
> some lines below ...
>
> Mmm, first this command *shouldn't* work like printed *OR*
> you are testing it while on "/" ?
> And I don't agree that 'more' would act here *between* the
> archiving and the verify parts :-)
> I guess if you try the test on a set with a number of elements
> smaller than your terminal number of lines you will see that the
> 'more' doesn't block ...
>
>
>>then on another session I delete filename2
>>$ rm filename2
>>
>>then back to the first session I proceed
>>[spacebar], etc.
>>Now there schould be a problem, right?
>>Because filename2 is in the tar archive, but no longer on the
>>file system!
>
>
> Well, you have the explaination of why not, a few lines above,
> but even if you'd patch the tar source to make it wait before
> the verify part it maybe would not be what you think, see
> http://www.gnu.org/software/tar/manu..._9.html#SEC151
> And read the twisted passage about in-memory cache.
>
>>'tar-1.14-i486-4' produces an error, like it should do,
>>but 'tar-1.15.1-i486-1' does not find any problem!
>
>
> That'd be related to the cache, though I can't much guess why
> the 1.14 would flush it faster, then maybe your archive size is huge
> and you just accidentally passed the threshold at that time ?
>
>
> (*URGENTMODE*)
>
> Now, back to your problem, you say that
>
>>(or $ tar cvP --verify -f /usr/backups/username/backup.tar
>>/home/username/*tar)
>>
>>both don't produce errors anymore, but
>>--verify, --compare, --diff, -d or -W just don't work!
>
>
> What do you mean by "just don't work!" ?
> ( sorry but I can't read your monitor from here :-) )
>
> What is the output for this command ?
> $ tar cvP --verify -f /usr/backups/username/backup.tar /home/username/*tar
>
> Or if it a huge print to post just quote the part that makes
> you say: "it doesn't work!"
> ( or test it with a small subset of dir/files )
>
> Hold on !-)

Ok.
This is going to take some time I understand.
First I'm going to study and then I come back to you guys.
But, for sure there is a difference in behavior between
'tar-1.14-i486-4' and 'tar-1.15.1-i486-1' ....
And that's quite annoying