to configure it out.
c. What other configuration/tuning is available.
Any other information or documentation is appreciated.
Thanks.
Regards.
Krishna Harathi
--
Check out the vibrant tech community on one of the world's most
_64-linux-gnu/libc.so.6
> #14 0x in ?? ()
> (gdb) print *node
> $4 = {left = 0x7fdfb64f1a40, right = 0x7fdf04665c80, parent = 3}
> (gdb) print parent
> $6 = (struct avltree_node *) 0x0
Thanks.
Regards.
Krishna Harathi
---
The main issue seems to be illegal state object in #2.
Looks like there are some recent changes in the latest code after 2.3.2.
Is this crash issue handled in the changes (
https://review.gerrithub.io/#/c/230990/) ?
Regards.
Krishna Harathi
On Sun, May 15, 2016 at 3:52 PM, Krishna Harathi
ource1/oneblox/repos/packaging/nfs-ganesha-2.3.2/nfs-ganesha-2.3.2/src/support/fridgethr.c:561
> #7 0x7f86416dfb50 in start_thread () from
> /lib/x86_64-linux-gnu/libpthread.so.0
> #8 0x7f8640dbd7bd in clone () from /lib/x86_64-linux-gnu/libc.so.6
> #9 0x in ?? ()
I have the core, let me know if you want me to look at any other
information in it.
Regards.
Krishna Harathi
On Wed, May 4, 2016 at 8:26 AM, Soumya Koduri <skod...@redhat.com> wrote:
>
>
> On 05/04/2016 08:30 PM, Soumya Koduri wrote:
>
>> Hi Malahal,
>>
>> On
Soumya,
Thanks for taking time and pointing the fix, appreciated.
Regards.
Krishna Harathi
On Thu, Apr 28, 2016 at 10:52 PM, Soumya Koduri <skod...@redhat.com> wrote:
> Hi Krishna,
>
> yes. We had been reported similar issue earlier and Frank submitted a
> patch to fix it [1
= 0x0}}
> (gdb) print *xdrs
> $3 = {x_op = XDR_DECODE, x_ops = 0x7fe29d0adfc0, x_public =
> 0x7fe288a483e8, x_private = 0x7fe28881c0e0, x_lib = {0x2, 0x7fe288a47f80},
> x_base = 0x0, x_v = {vio_base = 0x0, vio_head = 0x0, vio_tail = 0x0,
> vio_wrap = 0x0},
> x_handy = 0, x_flags
/exports/nfs14 and /exports/nfs32 are two different file systems.
Regards.
Krishna Harathi
On Mon, Dec 14, 2015 at 1:27 PM, Frank Filz <ffilz...@mindspring.com> wrote:
> Are /exports/nfs14 and /exports/nfs32 different filesystems?
>
>
>
> If not, either export can be
There were no cross-junction operations in this case. It is possible that
exportid has been reassigned in the configuration, but the FSID is unique.
Regards.
Krishna Harathi
On Mon, Dec 14, 2015 at 6:08 AM, Daniel Gryniewicz <d...@redhat.com> wrote:
> Is it possible that a junction wa
= /exports/nfs32;
> Tag = nfs32;
> Protocols = 3;
> Export_Id = 12;
> Filesystem_Id = 95171467.242799336;
> Access_Type = RW;
> Squash= all;
> Anonymous_Uid = -2;
> Anonymous_Gid = -2;
> NFS_Commit= False;
> }
Re
that issue), question to you all is it possible to validate the handle by
making sure that the correct FSID is there in the slot as shown by
exportid?
We are using Ganesha 2.1.0 NFSv3 only, but I see that 2.3.0 code has not
changed much in this
specific area.
Regards.
Krishna Harathi
---
Frank,
The github has my email address, but it is set to "don't show my email
address".
I have changed the github profile now to "show" email to everyone, I think
you can see it now.
Regards.
Krishna Harathi
On Fri, Nov 6, 2015 at 11:28 AM, Frank Filz <ffilz...@mindsprin
that this topic was discussed before, I would like to know the
latest thoughts on this.
Any help and background information in this area is appreciated.
Regards.
Krishna Harathi
--
___
Nfs
Ok, found your fix - https://bugzilla.redhat.com/show_bug.cgi?id=1218422
I will test your fix with the test-cases we have.
Regards.
Krishna Harathi
On Fri, Jun 19, 2015 at 3:32 PM, Krishna Harathi khara...@exablox.com
wrote:
I will certainly pick up the fix and try it asap, thanks
I will certainly pick up the fix and try it asap, thanks for pointing it
out.
Regards.
Krishna Harathi
On Fri, Jun 19, 2015 at 11:50 AM, Omkar Joshi o...@hedviginc.com wrote:
check cache inode related bug which I had raised on red hat bugzilla. It
may be related to that... I have posted
of allocated-but-not-freed memory at the end on normal
exit, and that is usual for Ganehsa I guess?
Regards.
Krishna Harathi
On Wed, Jun 17, 2015 at 6:36 AM, Malahal Naineni mala...@us.ibm.com wrote:
Hi Krishna, The code doesn't seem to match exactly with V2.1.0 but it
does look like nfs3_remove
system limit, what is the cache inode setting. We are
using Ganesha 2.1.
Regards.
Krishna Harathi
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50
[fs-pathlen] != '/')
continue;
this-parent = fs;
Regards.
Krishna Harathi
On Tue, May 5, 2015 at 4:19 PM, Frank Filz ffilz...@mindspring.com wrote:
Could you see if the top patch in this branch fixes the problem?
https://github.com/ffilz/nfs
18 matches
Mail list logo
