Chuck Lever wrote on 07/13/2018 07:36 AM:
You should be able to mount using "proto=tcp" with your mlx4 cards.
That avoids the use of NFS/RDMA but would enable the use of the
higher bandwidth network fabric.
Thanks I could definitely try that. IPoIB has it's own set of issues
though but can cross that bridge when I get to it....
Can you diagram your full configuration during the backup?
The main server in relation to this issue, which is named "pac" in the
log files, has several local storage devices which are exported over the
Ethernet and Infiniband interfaces. In addition, it has several other
mounts over Ethernet to some of our other NFS servers. The
rsnapshot/backup job uses rsync to read from the local storage and sends
to the NFS mounts to another server using standard 1Gb ethernet and TCP
protocol. So the answer to your second question,
Does the
NFS client mount the NFS server on this same host?
I believe is "yes"
Does it use
NFS/RDMA or can it use ssh instead of NFS?
Currently just uses NFS/TCP over 1Gb Ethernet link. rsnapshot does have
the ability to use SSH
I'm not familiar with the CentOS bug database. If there's an "NFS"
category, I would go with that.
There is no "NFS" category, only nfs-utils, nfs-utils-lib, and
nfs4-acl-tools. So I'm guessing if we want to report against NFS then
"kernel" would be the category?
Before filing, you should search that database to see if there are
similar bugs. Simply Googling "peername failed!" brings up several
NFSD related entries right at the top of the list that appear
similar to your circumstance (and there is no mention of NFS/RDMA).
Thanks I will be checking that out
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
