Bug 1162805 - A disperse 2 x (2 + 1) = 6 volume, kill two glusterfsd program, ls mountpoint abnormal.
Summary: A disperse 2 x (2 + 1) = 6 volume, kill two glusterfsd program, ls mountpoin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Xavi Hernandez
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1161066
TreeView+ depends on / blocked
 
Reported: 2014-11-11 17:51 UTC by Xavi Hernandez
Modified: 2015-05-14 17:44 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.7.0
Clone Of: 1161066
Environment:
Last Closed: 2015-05-14 17:28:25 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Xavi Hernandez 2014-11-11 17:51:15 UTC
+++ This bug was initially created as a clone of Bug #1161066 +++

Description of problem:
In a disperse 2 x (2 + 1) = 6 volume, kill two glusterfsd program, then ls mountpoint abnormal.for example:

ls /mnt/test/
s0  s0 s1  s2  s2  s3  s4  s4


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

How reproducible:


Steps to Reproduce:
1.
Volume Name: test
Type: Distributed-Disperse
Volume ID: efa68313-7476-46fd-b47d-478c5348f92c
Status: Started
Number of Bricks: 2 x (2 + 1) = 6
Transport-type: tcp
Bricks:
Brick1: 10.10.101.111:/sda
Brick2: 10.10.101.111:/sdb
Brick3: 10.10.101.111:/sdc
Brick4: 10.10.101.111:/sdd
Brick5: 10.10.101.111:/sde
Brick6: 10.10.101.111:/sdf
2. create many files and directorys in mountpoint.
3.kill brick5 and brick6
4.ls mountpoint abnormal.

Actual results:
ls /mnt/test/
s0  s0 s1  s2  s2  s3  s4  s4

Expected results:
ls /mnt/test/
s0 s1  s2  s3 s4

Additional info:

Comment 1 Anand Avati 2014-11-11 17:51:46 UTC
REVIEW: http://review.gluster.org/9098 (ec: Fix return values when not enough bricks) posted (#1) for review on master by Xavier Hernandez (xhernandez)

Comment 2 Anand Avati 2014-11-12 17:20:21 UTC
REVIEW: http://review.gluster.org/9098 (ec: Fix return errors when not enough bricks) posted (#2) for review on master by Xavier Hernandez (xhernandez)

Comment 3 Xavi Hernandez 2014-11-12 17:24:19 UTC
This latest patch should solve the problem.

Comment 4 Anand Avati 2014-11-18 16:42:03 UTC
REVIEW: http://review.gluster.org/9098 (ec: Fix return errors when not enough bricks) posted (#3) for review on master by Xavier Hernandez (xhernandez)

Comment 5 Anand Avati 2014-11-25 11:49:16 UTC
REVIEW: http://review.gluster.org/9098 (ec: Fix return errors when not enough bricks) posted (#4) for review on master by Xavier Hernandez (xhernandez)

Comment 6 Anand Avati 2014-12-03 15:28:21 UTC
REVIEW: http://review.gluster.org/9098 (ec: Fix return errors when not enough bricks) posted (#5) for review on master by Xavier Hernandez (xhernandez)

Comment 7 Anand Avati 2014-12-03 15:50:00 UTC
REVIEW: http://review.gluster.org/9098 (ec: Fix return errors when not enough bricks) posted (#6) for review on master by Xavier Hernandez (xhernandez)

Comment 8 Anand Avati 2014-12-05 09:34:53 UTC
REVIEW: http://review.gluster.org/9098 (ec: Fix return errors when not enough bricks) posted (#7) for review on master by Xavier Hernandez (xhernandez)

Comment 9 Anand Avati 2014-12-05 11:39:22 UTC
COMMIT: http://review.gluster.org/9098 committed in master by Vijay Bellur (vbellur) 
------
commit 36236eecef55c710e1f11ba4a04fe01da67cab6a
Author: Xavier Hernandez <xhernandez>
Date:   Tue Nov 11 18:45:01 2014 +0100

    ec: Fix return errors when not enough bricks
    
    Changes introduced by this patch:
    
    * Fix an incorrect error propagation when the state of the life
      cycle of a fop returns an error.
    
    * Fix incorrect unlocking of failed locks.
    
    * Return ENOTCONN if there aren't enough bricks online.
    
    * In readdir(p) check that the fd has been successfully open by
      a previous opendir.
    
    Change-Id: Ib44f25a1297849ebcbab839332f3b6359f275ebe
    BUG: 1162805
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: http://review.gluster.org/9098
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 10 Niels de Vos 2015-05-14 17:28:25 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 11 Niels de Vos 2015-05-14 17:35:42 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 12 Niels de Vos 2015-05-14 17:38:04 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 13 Niels de Vos 2015-05-14 17:44:50 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.