| Summary: | ENINVAL while doing add-brick | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Anush Shetty <ashetty> |
| Component: | fuse | Assignee: | shishir gowda <sgowda> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | mainline | CC: | gluster-bugs, nsathyan, vbellur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-17 09:21:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | fuse |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Anush Shetty
2012-02-28 09:35:25 UTC
This seems to happen because of the brick processes running out reserved ports. All ops fail, as connections are broken. The work-around is to: 1. Start glusterd with --xlator-option *.rpc-auth-allow-insecure=on 2. set allow-insecure option for the volume 3. mount client with --xlator-option *.client-bind-insecure=on Closing the bug, as this is a known limitation, and a work-around is available. |