[Bugs] [Bug 1297280] 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=1297280

Krutika Dhananjay <kdhananj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(wuyl at hygenomics.c
                   |                            |om)



--- Comment #4 from Krutika Dhananjay <kdhananj at redhat.com> ---
(In reply to wuyl from comment #3)
> (In reply to Krutika Dhananjay from comment #2)
> > Hi,
> > 
> > Did you unmount and mount the volume again after enabling
> > consistent-metadata and before running tar again on the volume? If not,
> > could you just try that?
> > Here are the steps:
> > 
> > 1) Enable consistent-metadata: # gluster volume set <VOL>
> > cluster.consistent-metadata on
> > 
> > 2) Unmount the volume
> > 
> > 3) Remount the volume
> > 
> > 4) Run tar.
> > 
> > -Krutika
> 
> hello, Krutika:
> 
> yes, we unmount all clients, and then set the attributes. then remount again.
> 
> an interesting point is that after we mount back glusterfs, for the first
> repeat of tar commmand, warnings are reduced significantly. But during 2nd
> to 10th repeats of the tar, the amounts of warning can be seen increased.

That's interesting.
So I tried recreating the bug in vain on my setup.

Here are my steps:
1. Create a distributed replicated volume with bricks spread across multiple
nodes and start and mount it using FUSE protocol.
2. Copy linux tar ball into the root of the volume and untar it.
3. Run tar on the linux source tree root.

====> Tar throws 'File changed as we read it' warnings for multiple
files/directories. [EXPECTED]

4. Then I enabled consistent-metadata on the volume and ran tar again.

====> Tar threw 'File changed as we read it' for 3 directories. [EXPECTED]

5. Then I unmounted the volume and mounted it again and ran tar.

====> Tar ran to completion without any warnings.

6. I ran tar again just to see if during repeats the warnings are seen. But no,
it ran just fine.

7. Created a few files under some of the directories in the volume from a
different mount point and ran tar on the first mount point but it ran fine
without any warnings.


Is there anything that you are doing differently here? If there are additional
steps you are executing or have additional information about the test case (say
if IO was in progress on the directory being archived while tar was running),
could you please share that as well?

NOTE: If your intention is to merely make tar ignore these warnings, then you
can use the following command line option while invoking tar:
--warning=no-file-changed.

-Krutika

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