Bug 1062256
| Summary: | mount hangs, when all the bricks in replica group go down while writes are in progress | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vivek Agarwal <vagarwal> |
| Component: | glusterfs | Assignee: | Pranith Kumar K <pkarampu> |
| Status: | CLOSED DUPLICATE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.1 | CC: | grajaiya, nlevinki, pkarampu, rcyriac, sankarshan, sasundar, sdharane, sharne, smanjara, tkatarki, vagarwal, vbellur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.6.0.5-1 | Doc Type: | Known Issue |
| Doc Text: |
When all the bricks in replica group go down while writes are in progress on that replica group, the mount may hang. Workaround: Kill the mount process, perform a lazy unmount of the existing mount and remount.
|
Story Points: | --- |
| Clone Of: | 1061580 | Environment: | |
| Last Closed: | 2014-05-30 06:26:25 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: | 1061580, 1063190 | ||
| Bug Blocks: | 1035040 | ||
|
Comment 2
Shalaka
2014-02-10 09:15:41 UTC
Modifying the bug summary, as this no longer relevant to server-quorum only, as per https://bugzilla.redhat.com/show_bug.cgi?id=1061580#c25 Please review the doc text and sign off. When all the bricks in replica group go down while writes are in progress *on that replica group*, the mount may hang. Workaround: Kill the mount process and remount. Added some text in '*' just add that part and we are good to go. Updated the doc text as suggested by Satheesaran. This bug was initially cloned for doc effort to add this bug under known issue. The exact bug was actually handled with this BZ, https://bugzilla.redhat.com/show_bug.cgi?id=1061580 I would prefer marking this bug as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1061580 This is a duplicate of the https://bugzilla.redhat.com/show_bug.cgi?id=1061580, seems fine with me (In reply to Vivek Agarwal from comment #10) > This is a duplicate of the > https://bugzilla.redhat.com/show_bug.cgi?id=1061580, seems fine with me Thanks, marking this bug as the duplicate *** This bug has been marked as a duplicate of bug 1061580 *** |