[Bugs] [Bug 1273272] New: tiering + nfs-ganesha: tiering has a segfault

bugzilla at redhat.com bugzilla at redhat.com
Tue Oct 20 06:34:32 UTC 2015


            Bug ID: 1273272
           Summary: tiering + nfs-ganesha: tiering has a segfault
           Product: GlusterFS
           Version: 3.7.5
         Component: tiering
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: saujain at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org

Description of problem:
While executing the fs-sanity test suite, the tiering volume throws a segfault

Version-Release number of selected component (if applicable):

How reproducible:
happen to be first time

Steps to Reproduce:
1. create volume of dist-rep type with tiering enabled.
2. export the volume for nfs-ganesha and mount it with vers=4
3. start executing the fs-sanity test suite

Actual results:
[2015-10-19 16:14:14.701640] E [MSGID: 109037] [tier.c:951:tier_start]
0-vol2-tier-dht: Demotion failed!
[2015-10-19 16:16:00.720267] I [MSGID: 109038]
[tier.c:586:tier_build_migration_qfile] 0-vol2-tier-dht: Failed to remove
pending frames:
frame : type(0) op(0)
frame : type(0) op(0)
frame : type(0) op(0)
patchset: git://git.gluster.com/glusterfs.git
signal received: 11
time of crash: 
2015-10-19 16:16:00
configuration details:
argp 1
backtrace 1
dlfcn 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.7.5

(gdb) bt
#0  __strlen_sse2 () at ../sysdeps/x86_64/strlen.S:31
#1  0x00007fc0cc3e4001 in gf_sql_query_function (prep_stmt=0x7fc0a042b288,
query_callback=query_callback at entry=0x7fc0cca0d640 <tier_gf_query_callback>,
_query_cbk_args=_query_cbk_args at entry=0x7fc0b17f9e70)
    at gfdb_sqlite3_helper.c:1157
#2  0x00007fc0cc3e55d0 in gf_sqlite3_find_unchanged_for_time
(db_conn=0x7fc0a0445440, query_callback=0x7fc0cca0d640
<tier_gf_query_callback>, query_cbk_args=0x7fc0b17f9e70,
    at gfdb_sqlite3.c:809
#3  0x00007fc0cc3dfbd1 in find_unchanged_for_time (_conn_node=<optimized out>,
query_callback=0x7fc0cca0d640 <tier_gf_query_callback>,
_query_cbk_args=0x7fc0b17f9e70, for_time=0x7fc0b17f9e60)
    at gfdb_data_store.c:506
#4  0x00007fc0cca0f947 in tier_process_brick_cbk (args=<synthetic pointer>,
local_brick=0x7fc0b8003680) at tier.c:501
#5  tier_build_migration_qfile (is_promotion=_gf_false,
query_cbk_args=0x7fc0b17f9e70, args=0x7fc0c501ecc0) at tier.c:606
#6  tier_demote (args=0x7fc0c501ecc0) at tier.c:666
#7  0x00007fc0d99e4df5 in start_thread (arg=0x7fc0b17fa700) at
#8  0x00007fc0d932b1ad in clone () at

# gluster volume status vol2
Status of volume: vol2
Gluster process                             TCP Port  RDMA Port  Online  Pid
Hot Bricks:
Brick    49158     0          Y       16128
Brick    49159     0          Y       30149
Brick    49159     0          Y       23716
Brick    49159     0          Y       19532
Cold Bricks:
Brick         49158     0          Y       19412
Brick         49158     0          Y       23610
Brick         49158     0          Y       30053
Brick         49157     0          Y       16026

Task Status of Volume vol2
Task                 : Tier migration      
ID                   : 1dd3374a-f0d5-4aa0-8a79-c1a2776ed72e
Status               : in progress         

Expected results:
no coredump expected

Additional info:
Not very which test in the test-suite caused the issue

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