Red Hat Bugzilla – Bug 1251291
tar on a glusterfs mount displays "file changed as we read it" even though the file was not changed
Last modified: 2017-03-08 05:49:39 EST
Description of problem:
tar command on the glusterfs mount point is seen to report the following error on some files -
tar: /usr/portage/app-accessibility/festival: file changed as we read it
Version-Release number of selected component (if applicable):
Very Easily reproducible.
Steps to Reproduce:
1. tar czvf /tmp/foo.tgz /path/to/files/in/gluster/mountpoint
While the tar command is running, the above described messages are seen for many files.
tar should run without seeing the above messages
Also, while editing files using vi in a gluster mountpoint, vi exhibits "The file changed since the last time it was read, when going to save the file."
Bug ID 1212842 was originally opened by someone else for this problem, but was closed by the developers as being fixed, but it's not fixed, the problem still exists.
Couple of questions:
1) Were files under modification while tar was running because of IO from the applications?
2) If the answer to 1) is a "No", did you enable cluster.consistent-metadata on the volume, unmount, remount the volume and then try running tar again? If not, could you do that?
Here's how you enable consistent-metadata:
# gluster volume set <VOL> cluster.consistent-metadata on
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.
Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.