[Bugs] [Bug 1058526] tar keeps reporting "file changed as we read it" on random files

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1058526

l a walsh <redhat at tlinx.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |redhat at tlinx.org



--- Comment #25 from l a walsh <redhat at tlinx.org> ---
This error also shows when I do a "tar" from a cifs file system.

It seems to be happening with nearly every file:

in @  206 MiB/s, out @  206 MiB/s, 35.0 GiB total, buffer   0% fulltar:
Data/Textures/IE/nm/more2: file changed as we read it
in @  218 MiB/s, out @  218 MiB/s, 35.4 GiB total, buffer   0% fulltar:
Data/Textures/IET/m: file changed as we read it
in @  216 MiB/s, out @  218 MiB/s, 35.9 GiB total, buffer   0% fulltar:
Data/Textures/Imp/m: file changed as we read it
in @  176 MiB/s, out @  176 MiB/s, 37.3 GiB total, buffer   0% fulltar:
Data/Textures/LLOD/Gen: file changed as we read it
in @  216 MiB/s, out @  218 MiB/s, 37.5 GiB total, buffer   0% full
....

The WIN7-workstation I am copying this from (x64-sp1,NTFS) is about as
idle as it gets, as I watch the "backup" work.  The NTFS has "access times"
turned off.

The output from tar (GNU tar 1.28), is being redirected/piped
into "mbuffer" which is using direct-I/O to save it to disk.

It seems like the bug is still present in tar V 1.28, (kernel=4.4.3).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ffjOEMUDSW&a=cc_unsubscribe