Bug 1203629 - DHT:Quota:- brick process crashed after deleting .glusterfs from backend
Summary: DHT:Quota:- brick process crashed after deleting .glusterfs from backend
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1183988 1217419 1217432
TreeView+ depends on / blocked
 
Reported: 2015-03-19 09:57 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:48 UTC (History)
10 users (show)

Fixed In Version: glusterfs-3.7.0
Clone Of: 1183988
: 1217419 1217432 (view as bug list)
Environment:
Last Closed: 2015-05-14 17:29:22 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2015-03-19 10:23:21 UTC
REVIEW: http://review.gluster.org/9941 (posix: handle failure from posix_resolve) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Anand Avati 2015-03-25 11:50:55 UTC
REVIEW: http://review.gluster.org/9941 (posix: handle failure from posix_resolve) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 3 Anand Avati 2015-03-25 16:11:38 UTC
COMMIT: http://review.gluster.org/9941 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 18dd162e00c8655648cea702bdb7b8bf25f1da97
Author: vmallika <vmallika>
Date:   Thu Mar 19 07:02:24 2015 +0530

    posix: handle failure from posix_resolve
    
    When building ancestory, posix_resolve gets the inode
    from the gfid. We need to handle the failure case from
    this function
    
    Change-Id: I19f0f0c739686b1b0ef96309212aa1c7911b3589
    BUG: 1203629
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/9941
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>

Comment 4 Niels de Vos 2015-05-14 17:29:22 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 5 Niels de Vos 2015-05-14 17:35:54 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 6 Niels de Vos 2015-05-14 17:38:16 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 7 Niels de Vos 2015-05-14 17:46:37 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.