Red Hat Bugzilla – Bug 1277359
Data Tiering:Filenames with spaces are not getting migrated at all
Last modified: 2016-09-17 11:39:54 EDT
+++ This bug was initially created as a clone of Bug #1263619 +++
Description of problem:
Files which have spaces in their names are not getting demoted at all.
Looks like the delimiter was set.
I created some files with spaces in names which are not getting demoted, but files with no spaces in name were getting demoted.
For Eg:If I had a filename as "coca cola drink.txt", it was throwing following errors in tier log
[2015-09-16 10:06:40.801876] E [MSGID: 109037] [tier.c:194:tier_migrate_using_query_file] 0-ruby-tier-dht: failed parsing coca
[2015-09-16 10:06:40.801887] E [MSGID: 109037] [tier.c:194:tier_migrate_using_query_file] 0-ruby-tier-dht: failed parsing cola
[2015-09-16 10:06:40.801888] E [MSGID: 109037] [tier.c:194:tier_migrate_using_query_file] 0-ruby-tier-dht: failed parsing drink
Version-Release number of selected component (if applicable):
[root@zod glusterfs]# rpm -qa|grep gluster
[root@zod glusterfs]# gluster --version
glusterfs 3.7.4 built on Sep 12 2015 01:35:35
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.
Steps to Reproduce:
1.create a vol with quota enabled and attach tier vol and set ctr on
2.set promo freq to say 100sec and demote to say 1000sec
3.Now create files with names having spaces.
4. Now don't access these files for say about 5min. This should mean they be demoted to cold.
But this doesnt happen and tier logs says "failed to parse"
1)I have tried on both nfsv3 and fuse with different combinations of spaces and some special characters. Now they are getting promoted/demoted.
hence moving to verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.