Bug 1707200 - VM stuck in a shutdown because of a pending fuse request
Summary: VM stuck in a shutdown because of a pending fuse request
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: write-behind
Version: 4.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1702686 1705865 1707195 1707198
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-07 02:54 UTC by Raghavendra G
Modified: 2019-07-11 09:05 UTC (History)
8 users (show)

Fixed In Version:
Clone Of: 1707195
Environment:
Last Closed: 2019-05-28 11:03:55 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22670 0 None Merged performance/write-behind: remove request from wip list in wb_writev_cbk 2019-05-28 11:03:54 UTC

Comment 1 Worker Ant 2019-05-07 05:17:08 UTC 
REVIEW: https://review.gluster.org/22670 (performance/write-behind: remove request from wip list in  wb_writev_cbk) posted (#1) for review on release-4.1 by Raghavendra G
Comment 2 Worker Ant 2019-05-28 11:03:55 UTC 
REVIEW: https://review.gluster.org/22670 (performance/write-behind: remove request from wip list in wb_writev_cbk) merged (#2) on release-4.1 by Raghavendra G
Comment 3 hari gowtham 2019-07-11 09:05:07 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-4.1.9, please open a new bug report.

glusterfs-4.1.9 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] https://lists.gluster.org/pipermail/gluster-users/2019-June/036679.html
[2] https://www.gluster.org/pipermail/gluster-users/
Note You need to log in before you can comment on or make changes to this bug.