Bug 1194733
| Summary: | 3.0.4 : Multithreaded Epoll : Volume does not start after adding bricks. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Amit Chaurasia <achauras> |
| Component: | glusterfs | Assignee: | Gaurav Kumar Garg <ggarg> |
| Status: | CLOSED NOTABUG | QA Contact: | Amit Chaurasia <achauras> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.0 | CC: | achauras, amukherj, annair, mzywusko, nbalacha, nlevinki, nsathyan, rcyriac, smohan, vagarwal, vbellur |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-30 05:32:18 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: | |||
|
Description
Amit Chaurasia
2015-02-20 16:12:23 UTC
Additionally, there is no connectivity between the cluster nodes. [root@dht-rhs-23 ~]# gluster peer status Number of Peers: 1 Hostname: 10.70.47.174 Uuid: 7e0465e6-029a-4052-bfdb-1b8db2cbdb47 State: Peer Rejected (Connected) Sos reports are @http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1194733/ Amit, Please provide permission to these files. In sos report "etc-glusterfs-glusterd.vol.log" glusterd logs files contain no logs. we need glusterd logs to analysis this bug. And in your volume status command, all of your brick are offline so it will not mount the volume. please provide necessary information. I have copied /var/log/glusterfs of both nodes at the above location. Please have a look. Just note that this might also contain recent operations carried out after this issue. If these logs are still not helpful, please let me know. I plan to try and reproduce the issue with different settings. I have copied /var/log/glusterfs of both nodes at the above location. Please have a look. Just note that this might also contain recent operations carried out after this issue. If these logs are still not helpful, please let me know. I plan to try and reproduce the issue with different settings. in your sos report glusterd logs are empty. we need glusterd logs to analysis this bug. these logs still not helpful. can you reproduce this bug and attach sos report again. Amit, Since the log files were rotated and sosreport doesn't capture all the log files until an explicit -all option provided, the current log files are insufficient to analyze the issue. Please try to reproduce it otherwise we would have to close this BZ. ~Atin |