+++ 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 glusterfs-client-xlators-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 glusterfs-api-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 glusterfs-fuse-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 glusterfs-debuginfo-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 glusterfs-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 glusterfs-server-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 glusterfs-cli-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 glusterfs-libs-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 [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. [root@zod glusterfs]# How reproducible: =============== easily 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"
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#5) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#6) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#7) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#8) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#9) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#10) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#11) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#12) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#13) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#14) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#15) for review on master by Joseph Fernandes
REVIEW: http://review.gluster.org/12354 (tier/libgfdb: Replacing ASCII query file with binary) posted (#16) for review on master by Joseph Fernandes
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user