[Bugs] [Bug 1212842] tar on a glusterfs mount displays "file changed as we read it" even though the file was not changed

[bugzilla at redhat.com]

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

Shruti Sampat <ssampat at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(ssampat at redhat.co |
                   |m)                          |



--- Comment #3 from Shruti Sampat <ssampat at redhat.com> ---
(In reply to Krutika Dhananjay from comment #2)
> Tried it about 9 times and was not able to hit the issue once.
> 
> Saw that your volume had quota enabled and tried the test again, this time
> with quota on. The bug is easily reproducible with quota enabled.The problem
> is unrelated to AFR. It could possibly be due to asynchronous updates to
> quota xattrs which happen in the background, leading to ctime modification
> of the file/directory while tar is in progress. Could you please verify the
> same and change the component to quota?

I was able to reproduce the issue in 1x2 replicate volume even with quota
turned off. Tried 10 times and was able to reproduce this issue 5 times. My
volume looks like this -

# gluster volume info rep

Volume Name: rep
Type: Replicate
Volume ID: 1e93f0f2-47d6-440b-86d6-3763bf8f97fc
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.70.37.126:/rhs/brick2/b1
Brick2: 10.70.37.123:/rhs/brick2/b1
Options Reconfigured:
features.uss: enable
client.event-threads: 4
server.event-threads: 5
cluster.consistent-metadata: on

Steps I performed -

1. Created the above volume with the volume options as seen above and started
it.

2. Mounted the volume using fuse.

3. On the mount point, download the linux kernel, followed by untar and then
tar-ing it again -

# wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.19.4.tar.xz; tar xf
linux-3.19.4.tar.xz; for i in {1..10}; do tar cf linux$i.tar linux-3.19.4 2>
tar$i.log; done

Out of 10 times, I saw this issue 5 times.

The issue is seen both on files and directories.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.