A lot of that looks very out-of-date. The description of what goes in
the Path statement is correct, but there is no longer an NFSv4_Proxy
section. Instead, configuration goes in the FSAL subsection of the
export. You can look at the sample proxy.conf in the repo here:
(And sorry for writing PSEUDO in my last email, I meant PROXY)
Daniel
On 1/28/19 12:29 PM, Jeff Becker wrote:
Hi,
On 1/25/19 5:36 AM, Daniel Gryniewicz wrote:
> The path given to PSEUDO needs to be the full path exported by the
> other NFS server, not any kind of local mount. So, when you mount the
> other server directly, you do this:
>
> mount -t nfs <server>:<remotepath> <localpath>
>
> What needs to go in that Path config statement is <remotepath> not
> <localpath>. PSEUDO isn't accessing a mount (and, indeed, you
> probably should not have the remote server mounted on the Ganesha
> box), it's acting as it's own NFS client, and translating NFS calls
> directly.
Thanks for the reply. To make sure I'm configuring this correctly, I'm
following directions at:
https://github.com/nfs-ganesha/nfs-ganesha/wiki/PROXY
Is that correct? Thanks again.
-Jeff
>
> Daniel
>
> On 1/24/19 6:10 PM, Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] wrote:
>> OK. I found some issues in my config file which I fixed. Now when I
>> try to start ganesha.nfsd, I get the following:
>>
>> 24/01/2019 15:03:50 : epoch 5c4a4456 : tpfe2 :
>> ganesha.nfsd-72287[main] init_export_root :EXPORT :CRIT :Lookup
>> failed on path, ExportId=12345 Path=/nex FSAL_ERROR=(No such file or
>> directory,2)
>> 24/01/2019 15:03:50 : epoch 5c4a4456 : tpfe2 :
>> ganesha.nfsd-72287[main] mdcache_exp_release :FSAL :INFO :Releasing
>> PROXY export 12345 for /pseudonex
>>
>> Yet it does exist
>>
>> bash-4.3# ls /nex
>> datapool datapoolne modules nex projects warasin
>>
>> What could be the problem? Thanks.
>>
>> Jeff
>>
>> ________________________________________
>> From: Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]
>> [jeffrey.c.becker(a)nasa.gov]
>> Sent: Thursday, January 24, 2019 2:55 PM
>> To: support(a)lists.nfs-ganesha.org
>> Subject: [non-nasa source] [NFS-Ganesha-Support] Re: NFS4 reexporter
>> question
>>
>> Sorry. Of course I meant the PROXY FSAL.
>> ________________________________________
>> From: Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC]
>> [jeffrey.c.becker(a)nasa.gov]
>> Sent: Thursday, January 24, 2019 2:39 PM
>> To: support(a)lists.nfs-ganesha.org
>> Subject: [non-nasa source] [NFS-Ganesha-Support] NFS4 reexporter
>> question
>>
>> Hello,
>>
>> I've built nfs-ganesha v2.7.1, and am trying to use the PSEUDO FSAL
>> to reexport an nfs4 mounted directory from the ganesha server to a
>> client. I used the base ganesha.conf (uncommenting out stuff I
>> needed), and followed the examples in
>> /usr/share/doc/packages/ganesha/config_samples/. The mount command on
>> the client succeeds but when I do an ls in the mountpoint dir,
>> there's nothing there. One issue is the client is also mounting the
>> filesystem directly from the same place the ganesha server is, but I
>> didn't think that mattered. I can send config files if needed. Please
>> help me get this working. Thanks.
>>
>> -Jeff
>> _______________________________________________
>> Support mailing list -- support(a)lists.nfs-ganesha.org
>> To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
>> _______________________________________________
>> Support mailing list -- support(a)lists.nfs-ganesha.org
>> To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
>> _______________________________________________
>> Support mailing list -- support(a)lists.nfs-ganesha.org
>> To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org
>>
> _______________________________________________
> Support mailing list -- support(a)lists.nfs-ganesha.org
> To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org