[Gluster-users] tar: File changed as we read it

[Andrew McGill]

  tar: blah.bleh: file changed as we read it

I have a file (two files actually) with different timestamps on the AFR 
backends -- I presume because the file timestamp was set to the current time, 
when the last write operation completed and there is some minor clock skew or 
network lag.  tar notices this intermittently, depending on which mirror 
handles the request.

It is a little distracting when tar most unreasonably complains about 
timestamps changing (what's wrong with a file having two timestamps that are 
really quite similar ?!)

Did I do something wrong, and is there a way to avoid this?  (FWIW, these 
files were written by rdiff-backup)

&:-)



Sometimes this ...

% tar -c file_statistics.2008-10-2* | tar -tv
-rw------- root/root     13393 2008-10-21 17:25:22 
file_statistics.2008-10-21T17:08:38+02:00.data.gz
tar: file_statistics.2008-10-21T17\:08\:38+02\:00.data.gz: file changed as we 
read it
-rw------- root/root     15185 2008-10-22 07:24:58 
file_statistics.2008-10-22T07:24:41+02:00.data.gz
tar: file_statistics.2008-10-22T07\:24\:41+02\:00.data.gz: file changed as we 
read it

Sometimes not ...

% tar -c file_statistics.2008-10-2* | tar -tv
-rw------- root/root     13393 2008-10-21 17:25:21 
file_statistics.2008-10-21T17:08:38+02:00.data.gz
-rw------- root/root     15185 2008-10-22 07:24:57 
file_statistics.2008-10-22T07:24:41+02:00.data.gz