Re: refuse to update certain files upon extraction

Lasse Kliemann <[email protected]> wrote:

> What could star prevent from overwriting existing files when invoked like 
> that:
>
>    star -xpU f=archive.tar
>
> ?
>
> I did some incremental dumps, restored them in a different filesystem and 
> compared to the original one. Level 0 is no problem. On higher levels, 
> however, certain files are not updated and hence differ from the current 
> original. I checked the archives, and they contain the files in question in 
> the correct version. But they are not extracted over the existing, outdated 
> files! Neither when I try with -xpU, nor when I try with -xpU -restore. 
> Extracting into an empty directory works (that way I found out that the files 
> inside of the archive are the correct ones).

Star has been tested _very_ often and _very_ complete with incremental backups 
and incremental restores. Since August 2004, more than 1000 incremental backups
and retores have been performed on the Berlios file server. We typically have 
~ 10 GB of changes per day and > ~ 2000 of renamed/removed files + an unknown
but large set of new files. Every day, a full compare is run between the 
original filesystem and the copy.

Since July 2005, no problem (except the directory timestamp problem from 
September 2007), not a single problem could be found. 

As star always writes an error message, you should start to run star from
script(1) to fetch such messages....

Jörg

-- 
 EMail:[email protected] (home) Jörg Schilling D-13353 Berlin
       [email protected]                (uni)  
       [email protected]     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily