Bug 1236563 - BVT: Seen a crash for marker, while running BVT
Summary: BVT: Seen a crash for marker, while running BVT
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: core
Version: rhgs-3.1
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Apeksha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-29 12:46 UTC by Apeksha
Modified: 2023-09-14 03:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-07 09:44:34 UTC
Embargoed:

Attachments (Terms of Use)

Description Apeksha 2015-06-29 12:46:21 UTC 
Description of problem:
BVT: Crash seen in marker while running BVT

Version-Release number of selected component (if applicable):
glusterfs-3.7.1-6.el6rhs.x86_64

How reproducible:
Once

Steps to Reproduce:
1. Run bvt on build - glusterfs-3.7.1-6.el6rhs.x86_64
2. Seen a crash

Backtrace of the core:

(gdb) bt
#0  0x00007f73c07b8f73 in mq_remove_contri () from /usr/lib64/glusterfs/3.7.1/xlator/features/marker.so
#1  0x00007f73c07b9a3c in mq_reduce_parent_size_task () from /usr/lib64/glusterfs/3.7.1/xlator/features/marker.so
#2  0x00007f73d04be1f2 in synctask_wrap () from /usr/lib64/libglusterfs.so.0
#3  0x00007f73cee268f0 in ?? () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()


Actual results: Seen a crash for marker

Expected results: No crashes

Additional info:
Comment 2 Apeksha 2015-06-29 12:59:39 UTC 
BVT job link : https://beaker.engineering.redhat.com/jobs/999046

Core and sosreports: http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1236563/
Comment 4 Anoop 2015-07-07 09:44:34 UTC 
Re-ran the BVT on glusterfs-3.7.1-7 build and did not see the crash, hence closing.
Comment 6 Red Hat Bugzilla 2023-09-14 03:01:17 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.