[Bugs] [Bug 1205709] New: ls command blocked when one brick disconnect, even reconnect.

bugzilla at redhat.com bugzilla at redhat.com
Wed Mar 25 13:46:56 UTC 2015


            Bug ID: 1205709
           Summary: ls command blocked when one brick disconnect, even
           Product: GlusterFS
           Version: mainline
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: jiademing.dd at gmail.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com

Description of problem:
   I use ten dd process to continueed write ten files in mountpoint,like this:
      dd if=/dev/zero of=/mountpoint/test/cnt.bak bs=1M &;   cnt={1,2,3....10}

   I disconnect one brick,then ls /mountpoint/test, this command 
blocked(longer than the timeout).I reconnected that brick, ls command still
   I kill `pidof dd`, the ls command return.

Version-Release number of selected component (if applicable):
  This problem also in 3.6.2

How reproducible:

Steps to Reproduce:
1.I create a disperse 3 redundancy 1 volume

Volume Name: test
Type: Disperse
Volume ID: bfdbfc8e-3dcc-4459-a1e4-9de17df03db5
Status: Started
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Brick1: node-1:/sda/
Brick2: node-2:/sdb/
Brick3: node-3:/sdc/
2.mkdir /mountpoint/test,then dd if=/dev/zero of=/mountpoint/test/cnt.bak bs=1M
3.disconnect node-3, ls /mountpoint/test

Actual results:
ls /mountpoint/test command blocked all the time.

Expected results:
ls /mountpoint/test command can return at soon.

Additional info:

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

More information about the Bugs mailing list