Displaying 4 results from an estimated 4 matches for "get_nfs_version".
2020 Apr 23
2
Looking for C8 AMD help
...or /repo/new did not match
Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts
"rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" =>
"rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr"
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
returning NFS(4,tcp) on host remotehost.my.domain
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
NFS(4,udp) failed for remotehost.my.domain: RPC: Unable to receive
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version:
NFS(3,udp) failed for remotehost.my.domain: RPC:...
2020 Apr 24
0
Looking for C8 AMD help
.../new did not match
> Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts "rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" => "rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr"
> Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: returning NFS(4,tcp) on host remotehost.my.domain
> Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: NFS(4,udp) failed for remotehost.my.domain: RPC: Unable to receive
> Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: NFS(3,udp) failed for remotehost.my.domai...
2018 May 22
1
[SOLVED] [Nfs-ganesha-support] volume start: gv01: failed: Quorum not met. Volume operation not allowed.
...lt;ffffffff81226d57>]
vfs_kern_mount+0x67/0x110
May 21 23:53:13 psql01 kernel: [<ffffffffc05e3846>]
nfs_do_root_mount+0x86/0xc0 [nfsv4]
May 21 23:53:13 psql01 kernel: [<ffffffffc05e3c44>]
nfs4_try_mount+0x44/0xc0 [nfsv4]
May 21 23:53:13 psql01 kernel: [<ffffffffc05826d7>] ?
get_nfs_version+0x27/0x90 [nfs]
May 21 23:53:13 psql01 kernel: [<ffffffffc058ec9b>]
nfs_fs_mount+0x4cb/0xda0 [nfs]
May 21 23:53:13 psql01 kernel: [<ffffffffc058fbe0>] ?
nfs_clone_super+0x140/0x140 [nfs]
May 21 23:53:13 psql01 kernel: [<ffffffffc058daa0>] ?
param_set_portnr+0x70/0x70 [nfs]
May...
2018 May 08
1
volume start: gv01: failed: Quorum not met. Volume operation not allowed.
On 4/11/2018 11:54 AM, Alex K wrote:
Hey Guy's,
Returning to this topic, after disabling the the quorum:
cluster.quorum-type: none
cluster.server-quorum-type: none
I've ran into a number of gluster errors (see below).
I'm using gluster as the backend for my NFS storage. I have gluster
running on two nodes, nfs01 and nfs02. It's mounted on /n on each host.
The path /n is