From: Olga Kornievskaia <aglo@umich.edu>
To: Naruto Nguyen <narutonguyen2018@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Cannot check if nfsv4 is running or not by rpcinfo
Date: Wed, 20 Mar 2019 10:08:47 -0400 [thread overview]
Message-ID: <CAN-5tyFBcBqS6mHTpf=oTbvf4BWRFk9J_On_8YVXTDPnHCJ2rQ@mail.gmail.com> (raw)
In-Reply-To: <CANpxKHExiJUMFBySUU0kixEV3d00Mo5Ze-matCans5JcOF5BhQ@mail.gmail.com>
This is a specific question related to that deployment.
rpcinfo -T tcp 172.17.5.13 100003 4 works for a typical linux client/server.
I suggest you contact Redhat to answer this specific question.
On Tue, Mar 19, 2019 at 11:53 AM Naruto Nguyen
<narutonguyen2018@gmail.com> wrote:
>
> Hi everyone,
>
> As the information from this link
> https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/storage_guide/#mount-shares-instance,
> I see that we have to query if Manila nfsv4 is running or not by:
>
> rpcinfo -T tcp -a 172.17.5.13.8.1 100003 4
>
> I cannot use
>
> rpcinfo -T tcp 172.17.5.13 100003 4
>
> It will be stuck and other command like " rpcinfo -T tcp -n 2049
> 172.17.5.13 nfs 4 leads to "rpcinfo: RPC: Port mapper failure - Timed
> out" but these commands are successful with nfsv3 and even on some
> other nfsv4, not Manila nfsv4.
>
> Could you please let me know why I cannot use other commands, but have
> to specify "8.1" (2049) in server address? Does it depend on nfs4
> server implementation or if we have any specification standard to
> query nfsv4 running?
>
> Thanks a lot
> Best regards,
> Naruto
prev parent reply other threads:[~2019-03-20 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 15:51 Cannot check if nfsv4 is running or not by rpcinfo Naruto Nguyen
2019-03-20 14:08 ` Olga Kornievskaia [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN-5tyFBcBqS6mHTpf=oTbvf4BWRFk9J_On_8YVXTDPnHCJ2rQ@mail.gmail.com' \
--to=aglo@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=narutonguyen2018@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).