-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unix socket mount error in /etc/fstab #331
Comments
Why’re you using transport type as unix? Please we use tcp or rdma or both as supported transport types for volumes. |
I only have two node , and the nginx+php is installed on the same machine. |
We don’t have that support as typically gluster client is run on a
different machine most of the times.
On Sun, 8 Oct 2017 at 13:13, Pigo ***@***.***> wrote:
I only have two node , and the nginx+php is installed on the same machine.
I think unix socket is faster than tcp , so I try to mount unix socket. I
have test performance use sybench , it's really a a little faster.
In CLI mode I can mount gluster via unix socket , but fstab can't , this
is my question , why CLI can but fstab can't do it ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#331 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGp7mELXklwMkPgR_MQ5k5yHTbpVR3vqks5sqH0qgaJpZM4Pxnsa>
.
--
- Atin (atinm)
|
Thank you for your contributions. |
Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it. |
I can use glusterfs mount unix socket in CLI mode , but can't mount in /etc/fstab
my fstab
the error log
I think the problem is "--volfile-id=/glustervol1.unix" , it append ".unix".
The text was updated successfully, but these errors were encountered: