Dear Users, I’m experiencing a random problem ( "file changed as we read it” error) during tar files creation on a distributed dispersed Gluster file system. The tar files seem to be created correctly, but I can see a lot of message similar to the following ones: tar: ./year1990/lffd1990050706p.nc.gz: file changed as we read it tar: ./year1990/lffd1990052106p.nc.gz: file changed as we read it tar: ./year1990/lffd1990052412p.nc.gz: file changed as we read it tar: ./year1990/lffd1990091018.nc.gz: file changed as we read it tar: ./year1990/lffd1990092300p.nc.gz: file changed as we read it tar: ./year1990/lffd1990092706p.nc.gz: file changed as we read it tar: ./year1990/lffd1990100312p.nc.gz: file changed as we read it tar: ./year1990/lffd1990100412.nc.gz: file changed as we read it tar: ./year1991/lffd1991012106.nc.gz: file changed as we read it tar: ./year1991/lffd1991010918.nc.gz: file changed as we read it tar: ./year1991/lffd1991011400.nc.gz: file changed as we read it I’m executing the tar command on a CentOS 6.2 operating system based server: it is a gluster native client. You can find below some basic info about the gluster client: [root@athena# rpm -qa|grep gluster glusterfs-3.10.5-1.el6.x86_64 centos-release-gluster310-1.0-1.el6.centos.noarch glusterfs-client-xlators-3.10.5-1.el6.x86_64 glusterfs-fuse-3.10.5-1.el6.x86_64 glusterfs-libs-3.10.5-1.el6.x86_64 Can I consider them as a false positive or the created tar files will suffer of inconsistence? Is it a tar command problem or a gluster problem? Could someone help me to resolve this issue? Thank you very much, Mauro |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
