[Bugs] [Bug 1302199] New: Scrubber crash (list corruption)

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1302199

            Bug ID: 1302199
           Summary: Scrubber crash (list corruption)
           Product: GlusterFS
           Version: 3.7.7
         Component: bitrot
          Assignee: bugs at gluster.org
          Reporter: vshankar at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:

Emmanuel reported a scrubber crash in NetBSD. Backtrace shows list corruption
when bitrot scrubber tries to fetch an item to scrub from a set of bricks.

Backtrace:

(gdb) bt
#0  0xbb213b74 in list_del_init (old=0x0) at
/home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/libglusterfs/src/list.h:87
#1  0xbb21682f in _br_scrubber_get_entry (child=0xbb106924, fsentry=0xb84fcfc0)
    at
/home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/xlators/features/bit-rot/src/bitd/bit-rot-scrub.c:1033
#2  0xbb2168b0 in _br_scrubber_find_scrubbable_entry (fsscrub=0xbb106cf0,
fsentry=0xb84fcfc0)
    at
/home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/xlators/features/bit-rot/src/bitd/bit-rot-scrub.c:1055
#3  0xbb216959 in br_scrubber_pick_entry (fsscrub=0xbb106cf0,
fsentry=0xb84fcfc0)
    at
/home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/xlators/features/bit-rot/src/bitd/bit-rot-scrub.c:1077
#4  0xbb216b0f in br_scrubber_proc (arg=<error reading variable: Cannot access
memory at address 0xb84fcfd8>)
    at
/home/jenkins/root/workspace/rackspace-netbsd7-regression-triggered/xlators/features/bit-rot/src/bitd/bit-rot-scrub.c:1153

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

How reproducible:
Intermittently

Steps to Reproduce:
Run the following test case:

    ./tests/bitrot/br-state-check.t

Actual results:
Test case fails at times and scrubber crashes

Expected results:
Test case should pass (and generate no cores)

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.