[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-tar] Bug? Where? Why? Why so many files changing as we read the
|
From: |
Pavel Raiskup |
|
Subject: |
Re: [Bug-tar] Bug? Where? Why? Why so many files changing as we read them? |
|
Date: |
Mon, 26 Oct 2015 08:13:05 +0100 |
|
User-agent: |
KMail/4.14.10 (Linux/4.2.3-300.fc23.x86_64; KDE/4.14.11; x86_64; ; ) |
On Sunday 25 of October 2015 20:23:57 Linda A. Walsh wrote:
> This may not be a tar bug, but I am trying to figure out
> what is going on and/or why so many 'changes'...
[..]
> Trying to run tar, as such:
>
> > tar cf ~/Appdata.tar --acls --xattrs Appdata
>
> And got **78** lines (out of 64389 files in 12357 directories)
> that claim "something changed".
> Note: I wasn't running any of the below related apps as tar ran:
> ....
> tar: Appdata/Local/Google/Chrome/User Data/Default/Cache: file changed
> as we read it
Try 'stat' on this file before/after running 'tar -c'. See '10.1.3 Race
conditions' section in documentation [1]. Either make sure tar is the
only process working with those files (globally as that is CIFS mount
point, not only on your machine) or pass there
'--warning=no-file-changed'.
[1] https://www.gnu.org/software/tar/manual/tar.html
Pavel