Bug 988642
Summary: | quota: hitting "D" state for dd command | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Raghavendra G <rgowdapp> |
Component: | write-behind | Assignee: | Raghavendra G <rgowdapp> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | gluster-bugs, rgowdapp, rhs-bugs, saujain, vbellur, vshastry |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.5.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 982629 | Environment: | |
Last Closed: | 2014-04-17 11:44:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 982629 | ||
Bug Blocks: |
Comment 1
Anand Avati
2013-07-26 03:45:57 UTC
REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#2) for review on master by Raghavendra G (rgowdapp) REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#3) for review on master by Raghavendra G (rgowdapp) REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#4) for review on master by Raghavendra G (rgowdapp) REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#5) for review on master by Raghavendra G (rgowdapp) REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#6) for review on master by Raghavendra G (rgowdapp) REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#7) for review on master by Raghavendra G (rgowdapp) REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#8) for review on master by Raghavendra G (rgowdapp) REVIEW: http://review.gluster.org/5398 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#9) for review on master by Raghavendra G (rgowdapp) COMMIT: http://review.gluster.org/5398 committed in master by Anand Avati (avati) ------ commit 1e49b3ac9b1019c742236be8db0ca8ec00750ae7 Author: Raghavendra G <rgowdapp> Date: Mon Jul 29 23:43:51 2013 +0530 performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies. * flush was queued behind some unfulfilled write. * A previously wound write returned an error and hence fd was marked bad with corresponding error. * wb_fulfill_head (invocation probably rooted in wb_flush), before winding checks for failures of previous writes and since there was a failure, calls wb_head_done without even winding one request in head. * wb_head_done unrefs all the requests in list "head". * since flush was last operation on fd (and most likely last operation on inode itself), no one invokes wb_process_queue and flush is stuck in request queue for eternity. Change-Id: I3b5b114a1c401d477dd7ff64fb6119b43fda2d18 BUG: 988642 Signed-off-by: Raghavendra G <rgowdapp> Reviewed-on: http://review.gluster.org/5398 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati> REVIEW: http://review.gluster.org/5883 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#1) for review on release-3.4 by Anand Avati (avati) REVIEW: http://review.gluster.org/5883 (performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies.) posted (#2) for review on release-3.4 by Anand Avati (avati) COMMIT: http://review.gluster.org/5883 committed in release-3.4 by Vijay Bellur (vbellur) ------ commit 8641a8641c4efec9cc7ac20108f2461a0300d01c Author: Raghavendra G <rgowdapp> Date: Mon Jul 29 23:43:51 2013 +0530 performance/write-behind: invoke request queue processing if we find fd marked bad while trying to fulfill lies. * flush was queued behind some unfulfilled write. * A previously wound write returned an error and hence fd was marked bad with corresponding error. * wb_fulfill_head (invocation probably rooted in wb_flush), before winding checks for failures of previous writes and since there was a failure, calls wb_head_done without even winding one request in head. * wb_head_done unrefs all the requests in list "head". * since flush was last operation on fd (and most likely last operation on inode itself), no one invokes wb_process_queue and flush is stuck in request queue for eternity. Change-Id: I3b5b114a1c401d477dd7ff64fb6119b43fda2d18 BUG: 988642 Signed-off-by: Raghavendra G <rgowdapp> Reviewed-on: http://review.gluster.org/5883 Tested-by: Gluster Build System <jenkins.com> 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.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |