MIME-Version: 1.0
References: <CANpxKHExiJUMFBySUU0kixEV3d00Mo5Ze-matCans5JcOF5BhQ@mail.gmail.com>
In-Reply-To: <CANpxKHExiJUMFBySUU0kixEV3d00Mo5Ze-matCans5JcOF5BhQ@mail.gmail.com>
From:   Olga Kornievskaia <aglo@umich.edu>
Date:   Wed, 20 Mar 2019 10:08:47 -0400
Message-ID: <CAN-5tyFBcBqS6mHTpf=oTbvf4BWRFk9J_On_8YVXTDPnHCJ2rQ@mail.gmail.com>
Subject: Re: Cannot check if nfsv4 is running or not by rpcinfo
To:     Naruto Nguyen <narutonguyen2018@gmail.com>
Cc:     Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

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