[Bugs] [Bug 1188471] New: When the volume is in stopped state/all the bricks are down mount of the volume hangs

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 3 01:33:47 UTC 2015


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

            Bug ID: 1188471
           Summary: When the volume is in stopped state/all the bricks are
                    down mount of the volume hangs
           Product: GlusterFS
           Version: 3.6.1
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: pkarampu at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    jiademing.dd at gmail.com
        Depends On: 1179180



+++ This bug was initially created as a clone of Bug #1179180 +++

Description of problem:
When all the bricks are down at the time of mounting the volume, then mount
command hangs. If only fragment number of bricks are up then mount takes
5 seconds to be successful.

root at pranithk-laptop - ~ 
17:12:37 :( ⚡ glusterd && gluster volume create ec2 disperse 3 redundancy 1
pranithk-laptop:/home/gfs/ec_{2,3,4} force
volume create: ec2: success: please start the volume to access data

root at pranithk-laptop - ~ 
17:12:42 :) ⚡ mount -t glusterfs pranithk-laptop:/ec2 /mnt/fuse1
^C

root at pranithk-laptop - ~ 
17:12:55 :( ⚡ ls /mnt/fuse1



^C^C^C

Command above hung, I had to kill the mount to get the prompt.

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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Anand Avati on 2015-01-06 06:49:19 EST ---

REVIEW: http://review.gluster.org/9396 (cluster/ec: Handle CHILD UP/DOWN in all
cases) posted (#1) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-01-08 12:20:38 EST ---

REVIEW: http://review.gluster.org/9396 (cluster/ec: Handle CHILD UP/DOWN in all
cases) posted (#2) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-01-28 04:05:14 EST ---

REVIEW: http://review.gluster.org/9396 (cluster/ec: Handle CHILD UP/DOWN in all
cases) posted (#3) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-01-28 08:06:45 EST ---

REVIEW: http://review.gluster.org/9396 (cluster/ec: Handle CHILD UP/DOWN in all
cases) posted (#4) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-01-28 10:53:56 EST ---

REVIEW: http://review.gluster.org/9396 (cluster/ec: Handle CHILD UP/DOWN in all
cases) posted (#5) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-01-28 22:49:59 EST ---

COMMIT: http://review.gluster.org/9396 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit a48b18d6f661f863371e625084a88a01aaf989f0
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Thu Jan 8 15:39:40 2015 +0530

    cluster/ec: Handle CHILD UP/DOWN in all cases

    Problem:
    When all the bricks are down at the time of mounting the volume, then mount
    command hangs.

    Fix:
    1. Ignore all CHILD_CONNECTING events comming from subvolumes.
    2. On timer expiration (without enough up or down childs) send
       CHILD_DOWN.
    3. Once enough up or down subvolumes are detected, send the appropriate
event.
       When rest of the subvols go up/down without changing the overall
       ec-up/ec-down send CHILD_MODIFIED to parent subvols.

    Change-Id: Ie0194dbadef2dce36ab5eb7beece84a6bf3c631c
    BUG: 1179180
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/9396
    Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>

--- Additional comment from Anand Avati on 2015-02-01 11:27:22 EST ---

REVIEW: http://review.gluster.org/9523 (cluster/ec: Wait for all bricks to
notify before notifying parent) posted (#1) for review on master by Pranith
Kumar Karampuri (pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-02-02 07:29:09 EST ---

REVIEW: http://review.gluster.org/9523 (cluster/ec: Wait for all bricks to
notify before notifying parent) posted (#2) for review on master by Pranith
Kumar Karampuri (pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-02-02 07:36:41 EST ---

REVIEW: http://review.gluster.org/9523 (cluster/ec: Wait for all bricks to
notify before notifying parent) posted (#3) for review on master by Pranith
Kumar Karampuri (pkarampu at redhat.com)

--- Additional comment from Anand Avati on 2015-02-02 15:21:57 EST ---

REVIEW: http://review.gluster.org/9523 (cluster/ec: Wait for all bricks to
notify before notifying parent) posted (#5) for review on master by Vijay
Bellur (vbellur at redhat.com)

--- Additional comment from Anand Avati on 2015-02-02 15:22:15 EST ---

COMMIT: http://review.gluster.org/9523 committed in master by Vijay Bellur
(vbellur at redhat.com) 
------
commit da1ff66255017501f54c50b3c40eeea11b5fc38f
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Sun Feb 1 15:03:46 2015 +0530

    cluster/ec: Wait for all bricks to notify before notifying parent

    This is to prevent spurious heals that can result in self-heal.

    Change-Id: I0b27c1c1fc7a58e2683cb1ca135117a85efcc6c9
    BUG: 1179180
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/9523
    Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>
    Tested-by: Vijay Bellur <vbellur at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1179180
[Bug 1179180] When the volume is in stopped state/all the bricks are down
mount of the volume hangs
-- 
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