Bug 1235231
Summary: | unix domain sockets on Gluster/NFS are created as fifo/pipe | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Niels de Vos <ndevos> | |
Component: | nfs | Assignee: | Niels de Vos <ndevos> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | mainline | CC: | bugs, gluster-bugs, udo.giacomozzi | |
Target Milestone: | --- | Keywords: | Reopened | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1244114 1244117 1244118 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:16:31 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: | ||||
Bug Blocks: | 1244114, 1244117, 1244118 |
Description
Niels de Vos
2015-06-24 11:06:29 UTC
REVIEW: http://review.gluster.org/11355 (nfs: a unix-domain-socket should not be created as fifo) posted (#5) for review on master by Niels de Vos (ndevos) REVIEW: http://review.gluster.org/11355 (nfs: a unix-domain-socket should not be created as fifo) posted (#6) for review on master by Niels de Vos (ndevos) REVIEW: http://review.gluster.org/11355 (nfs: a unix-domain-socket should not be created as fifo) posted (#7) for review on master by Niels de Vos (ndevos) REVIEW: http://review.gluster.org/11355 (nfs: a unix-domain-socket should not be created as fifo) posted (#8) for review on master by Niels de Vos (ndevos) Hi. I'm experiencing the exact same problem with Gluster 3.5.2 (Debian Package) and it's preventing my HA Proxmox Containers to operate properly (see http://forum.proxmox.com/threads/22767-var-log-not-working-in-containers) Is there any workaround or trick possible to avoid the problem? Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well. 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.8.0, please open a new bug report. glusterfs-3.8.0 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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |