[Bugs] [Bug 1260012] New: Data Tiering:Regression:New file creates still going to cold tier after attaching tier

[bugzilla at redhat.com]

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

            Bug ID: 1260012
           Summary: Data Tiering:Regression:New file creates still going
                    to cold tier after attaching tier
           Product: GlusterFS
           Version: 3.7.4
         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:
======================
while doing IOs, I attached a tier, and found that the new file creates are
still going to cold tier.
Also, after some time, when the volume was idle, I did a new set of file
creates, but still these file creates were still going to cold tier.

The vol was mounted on nfs.

Note: I didnt do any other file ops like read dir, ls,etc


Also see bug#1260003

[root at nag-manual-node1 glusterfs]# gluster --version
glusterfs 3.7.4 built on Sep  2 2015 18:06:07
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 nag-manual-node1 glusterfs]# rpm -qa|grep gluster
glusterfs-libs-3.7.4-0.16.git9f27ef9.el6.x86_64
glusterfs-api-3.7.4-0.16.git9f27ef9.el6.x86_64
glusterfs-client-xlators-3.7.4-0.16.git9f27ef9.el6.x86_64
glusterfs-fuse-3.7.4-0.16.git9f27ef9.el6.x86_64
glusterfs-cli-3.7.4-0.16.git9f27ef9.el6.x86_64
glusterfs-3.7.4-0.16.git9f27ef9.el6.x86_64
glusterfs-server-3.7.4-0.16.git9f27ef9.el6.x86_64




Steps to Reproduce:
=====================
1.create a regular volume
2.now mount vol and do IOs and while IOs are going on attach a tier 
3.now after attach tier is complete,do create anohter set of new files
4. still the files are going to cold tier.

note: no options were changed or set after vol create.

-- 
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.