[Bugs] [Bug 1212037] New: Data Tiering:Old copy of file still remaining on EC(disperse) layer, when edited after attaching tier(new copy is moved to hot tier)

[bugzilla at redhat.com]

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

            Bug ID: 1212037
           Summary: Data Tiering:Old copy of file still remaining on
                    EC(disperse) layer, when edited after attaching
                    tier(new copy is moved to hot tier)
           Product: GlusterFS
           Version: mainline
         Component: tiering
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
======================
When we attach a tier to a EC volume which has files already, then on trying to
edit those files using vim, the file with new contents is getting saved to the
hot tier, but the old tier still has the old version of file but renamed to
<filename>~
Eg:
If a file f2 was existing on ec volume and after attaching a tier, 
This means it will consume lot of disk space if they are huge files


Version-Release number of selected component (if applicable):
============================================================
[root at vertigo ~]# gluster --version
glusterfs 3.7dev built on Apr 13 2015 07:14:27
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.
[root at vertigo ~]# rpm -qa|grep gluster
glusterfs-server-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-rdma-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-api-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-regression-tests-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-devel-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-resource-agents-3.7dev-0.994.gitf522001.el6.noarch
glusterfs-libs-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-fuse-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-geo-replication-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-cli-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-api-devel-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-extra-xlators-3.7dev-0.994.gitf522001.el6.x86_64
glusterfs-debuginfo-3.7dev-0.994.gitf522001.el6.x86_64

How reproducible:
================
easily

Steps to Reproduce:
==================
1.create a EC volume
2.add files to it after mounting
3.Now attach a tier and try to edit one of those existing files, it can be seen
that while editing u get error, but on force edit, the  file with edited
contents get saved in hot tier, while the old file copy still exists as
<filename> ~ 


Additional info:
=================
[root at ninja ~]# ls /rhs/brick*/rhat*
/rhs/brick1/rhatvol-10:
f1  f10  f11  f12  f13  f14  f15  f16  f17  f18  f19  f2~  f20  f3  f4  f5  f6 
f7  f8  f9~

/rhs/brick1/rhatvol-2:
f1  f10  f11  f12  f13  f14  f15  f16  f17  f18  f19  f2~  f20  f3  f4  f5  f6 
f7  f8  f9~

/rhs/brick2/rhatvol-12:
f1  f10  f11  f12  f13  f14  f15  f16  f17  f18  f19  f2~  f20  f3  f4  f5  f6 
f7  f8  f9~

/rhs/brick2/rhatvol-4:
f1  f10  f11  f12  f13  f14  f15  f16  f17  f18  f19  f2~  f20  f3  f4  f5  f6 
f7  f8  f9~

/rhs/brick3/rhatvol-6:
f1  f10  f11  f12  f13  f14  f15  f16  f17  f18  f19  f2~  f20  f3  f4  f5  f6 
f7  f8  f9~

/rhs/brick3/rhatvol-tier:
f2  f9  newfile

/rhs/brick4/rhatvol-8:
f1  f10  f11  f12  f13  f14  f15  f16  f17  f18  f19  f2~  f20  f3  f4  f5  f6 
f7  f8  f9~

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