[Bugs] [Bug 1235216] New: tar on a glusterfs mount displays "file changed as we read it" even though the file was not changed
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jun 24 10:20:37 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1235216
Bug ID: 1235216
Summary: tar on a glusterfs mount displays "file changed as we
read it" even though the file was not changed
Product: GlusterFS
Version: mainline
Component: replicate
Keywords: Triaged
Severity: high
Assignee: bugs at gluster.org
Reporter: kdhananj at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com,
pkarampu at redhat.com, rcyriac at redhat.com,
ssampat at redhat.com, vagarwal at redhat.com
Depends On: 1212842, 1223757
Blocks: 1202842, 1223636
+++ This bug was initially created as a clone of Bug #1223757 +++
+++ This bug was initially created as a clone of Bug #1212842 +++
Description of problem:
-----------------------
tar command on the glusterfs mount point is seen to report the following error
on some files -
tar: ./linux-3.19.4/tools/perf/scripts/perl: file changed as we read it
There were no changes made to files while the tar command was in progress.
Reproducible on 1x2 volume. Unable to reproduce on a pure distribute volume.
See below for volume information -
# gluster v i test
Volume Name: test
Type: Replicate
Volume ID: f844808b-0d2e-40ce-9331-eddfb2b72855
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: vm5-rhsqa13:/rhs/brick5/b1
Brick2: vm6-rhsqa13:/rhs/brick5/b1
Options Reconfigured:
cluster.consistent-metadata: on
features.quota: on
features.uss: enable
client.event-threads: 4
server.event-threads: 5
Version-Release number of selected component (if applicable):
--------------------------------------------------------------
glusterfs-3.7dev-0.965.git2788ddd.el6.x86_64
How reproducible:
------------------
Tried a couple of times, on 6x3 and 1x2 volumes. Successfully reproducible.
Steps to Reproduce:
--------------------
1. Create replicate or distributed-replicate volume and set the option
`cluster.consistent-metadata' to on. Start the volume.
2. Fuse mount the volume.
3. Download linux kernel and untar it on the mount point.
4. Compile the kernel and try to create a tar.
Actual results:
----------------
While the tar command is running, the above described messages are seen for
many files.
Expected results:
------------------
tar is expected to run successfully.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1202842
[Bug 1202842] [TRACKER] RHGS 3.1 Tracker BZ
https://bugzilla.redhat.com/show_bug.cgi?id=1212842
[Bug 1212842] tar on a glusterfs mount displays "file changed as we read
it" even though the file was not changed
https://bugzilla.redhat.com/show_bug.cgi?id=1223636
[Bug 1223636] 3.1 QE Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1223757
[Bug 1223757] tar on a glusterfs mount displays "file changed as we read
it" even though the file was not changed
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list