This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.Hi All,
We are using a custom FSAL with NFS Ganesha 2.6.3 version and
libntirpc 1.6.3 version. We are consistently running into the following
crash in libntirpc and wondering if this is a known issue.
> reference to this particular issue. Can you point me in the direction of
> some more info please? Any idea how to workaround this issue on CentOS 7.5?
> I did try creating /etc/gai.conf but didn't seem to have any effect.
>
> On Wed, Sep 19, 2018 at 1:06 AM Naresh Babu wrote:
>
>> Upgrade
deprecated. Please subscribe to the new devel list at
>> lists.nfs-ganesha.org.
>> Oh, it looks like rpc.statd is refusing the connection because it
>> doesn't think ::1 (the IPv6 localhost address) is localhost. If so,
>> this would be either a bug or a misconfiguration in rpc.stat
on your system? If you ping :::10.0.0.7 on that box,
> does it work? If the problem is IPv6, you may be able to work around it
> by preferring IPv4 to IPv6. This is done by adding this line to
> /etc/gai.conf:
>
> precedence :::0:0/96 100
>
> Daniel
>
> On 09
This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.We have developed a custom FSAL on top of nfs-ganesha 2.5.4 version and
lock tests ran fine with that. But, after upgrading nfs-ganesha to 2.6.2,
lock tests are failing with the following errors:
Hi All,
Is there a reason for not implementing dump request in NFS
ganesha (mnt_Dump.c)? Is there a place where we track mount entries?
Thanks,
Naresh
--
Check out the vibrant tech community on one of the world's most
t; the ports being used by nlockmgr and statd (ports used shall be listed via
> cmd 'rpcinfo -p').
>
> Thanks,
> Soumya
>
> On 02/27/2017 05:03 AM, Naresh Babu wrote:
>
>> I don't see lockd process running on the system and I don't have any NFS
>> mounts.
>>
lock requests may
> go to kernel lockd.
>
> Regards, Malahal.
>
> On Sun, Feb 26, 2017 at 2:38 PM, Naresh Babu <snareshb...@gmail.com>
> wrote:
> > I ran into a very basic issue with file locking on ganesha nfs mount.
> When I
> > tried to issue a fcntl to lock a
I ran into a very basic issue with file locking on ganesha nfs mount. When
I tried to issue a fcntl to lock a file, the call hangs on client. NLM
request didn't get to ganesha.nfsd process (verified through gdb). Do I
need to enable something or install/copy something to get file locking
working
gt;>
>>
>>
>> With support_ex, an fd is associated with each file clients have open
>> (NFS v4), and additional fds are (may) be used per file/lock owner pair.
>>
>>
>>
>> Ultimately we do need to have a limit on how much state (NFS v4 open,
>>
10 matches
Mail list logo
