[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



--- Comment #23 from Pranith Kumar K <pkarampu at redhat.com> ---
(In reply to BugMasta from comment #20)
> Since people seem to think this is a trivial bug, and noone seems to care
> about it, I'll just point out here that this bug renders the exit status of
> tar utterly useless.

1 Engineer is NFS, 3 Engineers in replication and 3 Engineers in DHT are
working on this issue for the past 5 weeks.

> 
> Anyone who uses tar to zip up files on a glusterfs filesystem faces the
> problem that tar returns error status 1, and they then have to resort to
> other means to check whether the tarball is valid. VERY unsatisfactory.
> 
> Since tar is an absolutely vital tool for dealing with files, THIS IS A
> PROBLEM WHICH SHOULD NOT BE IGNORED.

This bug is difficult to fix. All the solutions we have now reduce the
performance for this consistency. We probably are going to give an option under
which things will fine. There is also a design change that we are looking for
the correct fix in the long term.

-- 
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=fAHb3eFvE6&a=cc_unsubscribe