[Bugs] [Bug 1242536] New: Data Tiering: Rename of file is not heating up the file

bugzilla at redhat.com bugzilla at redhat.com
Mon Jul 13 14:07:04 UTC 2015


            Bug ID: 1242536
           Summary: Data Tiering: Rename of file is not heating up the
           Product: GlusterFS
           Version: 3.7.2
         Component: tiering
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: josferna at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org, nchilaka at redhat.com
        Depends On: 1241054

+++ This bug was initially created as a clone of Bug #1241054 +++

nchilaka 2015-07-01 07:33:53 EDT

Description of problem:
When you rename a cold file, the file should get heated up and eventually move
to hot tier. But that is not happening.
This is a case of metadata change which means ideally it should increase the
counter of file to get heated up, but is not happening

Version-Release number of selected component (if applicable):
[root at tettnang ~]# gluster --version
glusterfs 3.7.1 built on Jun 28 2015 11:01:14
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.
[root at tettnang ~]# rpm -qa|grep gluster
[root at tettnang ~]# 

Steps to Reproduce:
1.create a regular volume and start it.
2.set following options
 performance.quick-read: off
performance.io-cache: off

3.Now attach a tier and enable features.ctr-enabled.
4. fuse mount the volume
5. Create a file and check if it is created in hot tier(works as expected)
6.  Now wait for say about 3min by keeping the setup idle.
7. Now the file should have been moved to cold tier(works as expected)
8.Now do a rename of the file

Actual results:
rename passes, but the file doesnt get heated,even though the ctime changes,
which is a metadata change action

I haven't set promote/demote freq. Which means the default time should be about
Also, I haven't turned on  features.record-counters or read/write threshold
counters, which means I file should get heated if modified even once.

Logs will be attached

Expected results:

Additional info:

--- Additional comment from Anand Avati on 2015-07-08 11:57:53 EDT ---

REVIEW: http://review.gluster.org/11584 (libgfdb/ctr: Fixing rename or update
of link) posted (#1) for review on master by Joseph Fernandes

--- Additional comment from Joseph Elwin Fernandes on 2015-07-08 12:51:45 EDT

Tested by abusing rename :) 

for i in {1..100000}; do mv file file1 ; mv file1 file;  done

--- Additional comment from Anand Avati on 2015-07-09 15:11:34 EDT ---

COMMIT: http://review.gluster.org/11584 committed in master by Dan Lambright
(dlambrig at redhat.com) 
commit 3c25f33162c981d18bf78d1fc3536496670959e9
Author: Joseph Fernandes <josferna at redhat.com>
Date:   Wed Jul 8 21:22:53 2015 +0530

    libgfdb/ctr: Fixing rename or update of link

    Fixing rename or updating of link in
    1) libgfdb : handling return from updatelink
    2) ctr xlator: correcting freeing of oldbase name in
                   hardlink list in the update link

    Change-Id: I1789c492b81876123cd456051a9ae495e876ad46
    BUG: 1241054
    Signed-off-by: Joseph Fernandes <josferna at redhat.com>
    Reviewed-on: http://review.gluster.org/11584
    Tested-by: Joseph Fernandes
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    Tested-by: Dan Lambright <dlambrig at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>

Referenced Bugs:

[Bug 1241054] Data Tiering: Rename of file is not heating up the file
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.

More information about the Bugs mailing list