Hi,
On 19/05/17 18:27, te-yamau...@usen.co.jp wrote:
I currently use version 3.10.2.
When nfs is enabled, the following warning is displayed.
Why is nfs-ganesha recommended?
Is there something wrong with gluster nfs?
Gluster NFS is being deprecated in favor of NFS-Ganesha Enter "yes" to
Here is the relevant Advisory for RHEL which just came in
https://access.redhat.com/errata/RHSA-2017:1263
-bill
On 5/21/2017 10:23 PM, Jiffin Tony Thottan wrote:
Forwarding mail to ganesha list
Adding Kaleb as well who usually build nfs-ganesha packages
On 21/05/17 07:52, W Kern wrote:
On 5/21/2017 7:00 PM, Ravishankar N wrote:
On 05/22/2017 03:11 AM, W Kern wrote:
gluster volume set VOL cluster.quorum-type none
from the remaining 'working' node1 and it simply responds with
"volume set: failed: Quorum not met. Volume operation not allowed"
how do you FORCE gluster to
Forwarding mail to ganesha list
Adding Kaleb as well who usually build nfs-ganesha packages
On 21/05/17 07:52, W Kern wrote:
I got bit by that during a maintenance session on a production NFS
server. I upgraded and got the same message.
libntirpc 1.4.4 is a security upgrade due to a DOS
On 05/22/2017 03:11 AM, W Kern wrote:
So I am experimenting with shards using a couple VMs and decided to
test his scenario (i.e. only one node available on a simple 2 node + 1
arbiter replicated/sharded volume use 3.10.1 on Cent7.3)
I setup a VM testbed. Then verified everything including
So I am experimenting with shards using a couple VMs and decided to test
his scenario (i.e. only one node available on a simple 2 node + 1
arbiter replicated/sharded volume use 3.10.1 on Cent7.3)
I setup a VM testbed. Then verified everything including the sharding
works and then shutdown
