Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-12 Thread Varghese Devassy 
I am moving to 2.3 very soon. In the meantime, I searched for the latest 
2.3 binary and source package and I see some of them at rpmfind.net. The 
latest version I see here is 2.3.1.4 (nfs-ganesha-2.3.1-4.el7.x86_64.rpm 
). 
But no source, debug and utils packages for 2.3 here. Any other sites 
that have the package downloads?


I see in another thread you mentioned 2.3.2. Is that going to be out 
soon? In that case, I can move to that directly...


Thanks

Varghese Devassy
v_deva...@yahoo.com

On 2016-04-12 02:00 PM, Malahal Naineni wrote:

Varghese Devassy [v_deva...@yahoo.com] wrote:

Thanks to all replies on this thread.

Initially, we had developed our FSAL based on Ganesha 2.1 but later
moved to 2.2 when we noticed that 2.1 binaries were not available.
However, when moving to 2.2 we noticed that there were changes in the
FSAL interface -- function prototypes etc... Since there is no more 2.2
support we are thinking of moving to 2.3. But, before we do that any
idea how much porting effort may be required to run a 2.2 FSAL against
2.3 Ganesha?

Porting to V2.3 should be easy as changes from V2.2 to V2.3 are
mostly bug fixes and some clean ups.

Regards, Malahal.



--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-12 Thread William Allen Simpson 
On 4/11/16 11:51 AM, Frank Filz wrote:
>> Thanks to all replies on this thread.
>>
>> Initially, we had developed our FSAL based on Ganesha 2.1 but later moved
>> to 2.2 when we noticed that 2.1 binaries were not available.
>> However, when moving to 2.2 we noticed that there were changes in the
>> FSAL interface -- function prototypes etc... Since there is no more 2.2
> support
>> we are thinking of moving to 2.3. But, before we do that any idea how much
>> porting effort may be required to run a 2.2 FSAL against
>> 2.3 Ganesha?
>
> The API changes should not be huge.
>
> There will be larger API changes in 2.5 or some future release. A new
> extended API is introduced in 2.4, however the old API is supported in
> parallel. At some point, the old API will be deprecated.
>
But there have been a tremendous number of bug fixes in 2.3 and 2.4.

If you are doing any new FSAL work, use the next as your base.
There's simply no excuse for doing anything else.

And of course, you could contribute the FSAL, so it would be in
the archive


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Frank Filz 
> On 04/11/2016 09:38 AM, Tushar Shinde wrote:
> > If 2.2 will be not maintained, which will be next stable release? I
> > don't see any branch "V2.4-stable". Which will be the next LTS stable
> > branch for NFS Ganesha?
> 
> 2.3 is the current stable release. 2.4 is winding down to release soon,
> probably in May.
> 
> There won't be a V2.4-stable branch until 2.4 is actually released.

And in fact, there may not actually be a V2.4-stable branch until there is a
patch for V2.4 after V2.4.0 has been tagged.

Our release protocol is as follows (with signed tags):

Vx.y-dev-nnn merges during development
Vx.y-rc-nn merges during final stages of development
Vx.y.0 signed tag at completion of development
Next branch merged into master (bringing master to Vx.y.0 tag)
Vx.y-stable branch opened at some point
Vx.z-dev-0 tag pushed to next branch at some point

Frank


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Varghese Devassy 
Thanks to all replies on this thread.

Initially, we had developed our FSAL based on Ganesha 2.1 but later 
moved to 2.2 when we noticed that 2.1 binaries were not available. 
However, when moving to 2.2 we noticed that there were changes in the 
FSAL interface -- function prototypes etc... Since there is no more 2.2 
support we are thinking of moving to 2.3. But, before we do that any 
idea how much porting effort may be required to run a 2.2 FSAL against 
2.3 Ganesha?

Thank you

Varghese Devassy
v_deva...@yahoo.com

On 2016-04-11 09:41 AM, Daniel Gryniewicz wrote:
> 2.3 is the current stable release.  2.4 is the next stable release.
> Ganesha doesn't currently do anything other than stable releases, nor
> does it have a normal/LTS distinction.  Releases are maintained as long
> as someone in the community needs them and is willing to maintain them.
>
> Daniel
>
> On 04/11/2016 09:38 AM, Tushar Shinde wrote:
>> If 2.2 will be not maintained, which will be next stable release? I
>> don't see any branch "V2.4-stable". Which will be the next LTS stable
>> branch for NFS Ganesha?
>>
>>
>> On Mon, Apr 11, 2016 at 5:53 PM, Kaleb S. KEITHLEY  
>> wrote:
>>> On 04/11/2016 02:06 AM, Soumya Koduri wrote:

 On 04/11/2016 06:41 AM, Varghese Devassy wrote:
> Soumya,
>
> Are there any plans of adding these missing fixes into 2.2?
 I am not sure if V2.2 branch is still being actively supported. Request
 Malahal/Kaleb to comment.

>>> AFAIK it's not supported/maintained. About 98% is devoted to 2.4/next,
>>> and 2% to maintaining 2.3.
>>>
>>> If someone needs 2.2 maintained and wants to devote cycles to it, I'm
>>> reasonably certain nobody would object.
>>>
>>> --
>>>
>>> Kaleb
>>>
>>> --
>>> Find and fix application performance issues faster with Applications Manager
>>> Applications Manager provides deep performance insights into multiple tiers 
>>> of
>>> your business applications. It resolves application problems quickly and
>>> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
>>> gampad/clk?id=1444514301=/ca-pub-7940484522588532
>>> ___
>>> Nfs-ganesha-devel mailing list
>>> Nfs-ganesha-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>> --
>> Find and fix application performance issues faster with Applications Manager
>> Applications Manager provides deep performance insights into multiple tiers 
>> of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
>> gampad/clk?id=1444514301=/ca-pub-7940484522588532
>> ___
>> Nfs-ganesha-devel mailing list
>> Nfs-ganesha-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>>
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301=/ca-pub-7940484522588532
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Tushar Shinde 
On Mon, Apr 11, 2016 at 7:43 PM, Kaleb S. KEITHLEY  wrote:
> 2.3 is the current stable release. 2.4 is winding down to release soon,
> probably in May.
>
> There won't be a V2.4-stable branch until 2.4 is actually released.


Thanks for clear details.

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Kaleb S. KEITHLEY 
On 04/11/2016 09:38 AM, Tushar Shinde wrote:
> If 2.2 will be not maintained, which will be next stable release? I
> don't see any branch "V2.4-stable". Which will be the next LTS stable
> branch for NFS Ganesha?

2.3 is the current stable release. 2.4 is winding down to release soon,
probably in May.

There won't be a V2.4-stable branch until 2.4 is actually released.

-- 

Kaleb

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Daniel Gryniewicz 
2.3 is the current stable release.  2.4 is the next stable release. 
Ganesha doesn't currently do anything other than stable releases, nor 
does it have a normal/LTS distinction.  Releases are maintained as long 
as someone in the community needs them and is willing to maintain them.

Daniel

On 04/11/2016 09:38 AM, Tushar Shinde wrote:
> If 2.2 will be not maintained, which will be next stable release? I
> don't see any branch "V2.4-stable". Which will be the next LTS stable
> branch for NFS Ganesha?
>
>
> On Mon, Apr 11, 2016 at 5:53 PM, Kaleb S. KEITHLEY  
> wrote:
>> On 04/11/2016 02:06 AM, Soumya Koduri wrote:
>>>
>>>
>>> On 04/11/2016 06:41 AM, Varghese Devassy wrote:
 Soumya,

 Are there any plans of adding these missing fixes into 2.2?
>>>
>>> I am not sure if V2.2 branch is still being actively supported. Request
>>> Malahal/Kaleb to comment.
>>>
>>
>> AFAIK it's not supported/maintained. About 98% is devoted to 2.4/next,
>> and 2% to maintaining 2.3.
>>
>> If someone needs 2.2 maintained and wants to devote cycles to it, I'm
>> reasonably certain nobody would object.
>>
>> --
>>
>> Kaleb
>>
>> --
>> Find and fix application performance issues faster with Applications Manager
>> Applications Manager provides deep performance insights into multiple tiers 
>> of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
>> gampad/clk?id=1444514301=/ca-pub-7940484522588532
>> ___
>> Nfs-ganesha-devel mailing list
>> Nfs-ganesha-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301=/ca-pub-7940484522588532
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Tushar Shinde 
If 2.2 will be not maintained, which will be next stable release? I
don't see any branch "V2.4-stable". Which will be the next LTS stable
branch for NFS Ganesha?


On Mon, Apr 11, 2016 at 5:53 PM, Kaleb S. KEITHLEY  wrote:
> On 04/11/2016 02:06 AM, Soumya Koduri wrote:
>>
>>
>> On 04/11/2016 06:41 AM, Varghese Devassy wrote:
>>> Soumya,
>>>
>>> Are there any plans of adding these missing fixes into 2.2?
>>
>> I am not sure if V2.2 branch is still being actively supported. Request
>> Malahal/Kaleb to comment.
>>
>
> AFAIK it's not supported/maintained. About 98% is devoted to 2.4/next,
> and 2% to maintaining 2.3.
>
> If someone needs 2.2 maintained and wants to devote cycles to it, I'm
> reasonably certain nobody would object.
>
> --
>
> Kaleb
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301=/ca-pub-7940484522588532
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Kaleb S. KEITHLEY 
On 04/11/2016 02:06 AM, Soumya Koduri wrote:
> 
> 
> On 04/11/2016 06:41 AM, Varghese Devassy wrote:
>> Soumya,
>>
>> Are there any plans of adding these missing fixes into 2.2?
> 
> I am not sure if V2.2 branch is still being actively supported. Request
> Malahal/Kaleb to comment.
> 

AFAIK it's not supported/maintained. About 98% is devoted to 2.4/next,
and 2% to maintaining 2.3.

If someone needs 2.2 maintained and wants to devote cycles to it, I'm
reasonably certain nobody would object.

-- 

Kaleb

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-11 Thread Soumya Koduri 


On 04/11/2016 06:41 AM, Varghese Devassy wrote:
> Soumya,
>
> Are there any plans of adding these missing fixes into 2.2?

I am not sure if V2.2 branch is still being actively supported. Request 
Malahal/Kaleb to comment.

Thanks,
Soumya

>
> Varghese Devassy
> v_deva...@yahoo.com
>
> On 2016-04-10 06:40 AM, Soumya Koduri wrote:
>> Hi,
>>
>> I had run into similar crash when cache inode entries get reaped.
>> Below patch had fixed the issue.
>>
>> https://review.gerrithub.io/#/c/258687/
>>
>> I think this patch is not merged into V2.2. Please check
>> nfs-ganesha-2.3 or current next branch packages.
>>
>> Thanks,
>> Soumya
>>
>> On 04/09/2016 05:54 AM, Varghese Devassy wrote:
>>> Hi,
>>>
>>> We have our own FSAL that runs in the following version of NFS ganesha
>>> on a CentOS system. I have been trying to locate a crash for the last
>>> few days but with no progress. Any help in this matter will be greatly
>>> appreciated.
>>>
>>> # rpm -qa | grep -i ganesha
>>> nfs-ganesha-2.2.0-6.el7.x86_64
>>> nfs-ganesha-utils-2.2.0-6.el7.x86_64
>>> nfs-ganesha-debuginfo-2.2.0-6.el7.x86_64
>>> #
>>>
>>> # uname -a
>>> Linux vcd-test1 3.10.0-327.3.1.el7.x86_64 #1 SMP Wed Dec 9 14:09:15 UTC
>>> 2015 x86_64 x86_64 x86_64 GNU/Linux
>>> #
>>>
>>> We have been having a crash when running ls -lR for a long periods of
>>> time (over 1+ hours). To make the crash earlier, we reduced the inode
>>> cache to 1 by introducing the following configuration parameter.
>>>
>>> CACHEINODE
>>> {
>>>   Entries_HWMark = 1;
>>> }
>>>
>>> With this change, I am able to get the crash in two ls commands with the
>>> following steps:
>>> 1. mount  /mnt
>>> 2. cd /mnt
>>> 3. ls
>>> 4. cd var
>>> 5. ls (ganesha crashes)
>>>
>>> It seems to me that the somehow the entry obtained from the cache has
>>> the wrong file handle for var directory. Because, I checked the FH in
>>> debugger and it has some FH values that seems wrong.
>>>
>>> The problematic dir_entry is retrieved at the following line in
>>> src/Protocols/NFS/nfs3_readdirplus.c
>>>
>>>   188 dir_entry =
>>> nfs3_FhandleToCache(&(arg->arg_readdirplus3.dir),
>>>   189 &(res->res_readdirplus3.status),
>>>   190   );
>>>
>>> Here is the stack trace.
>>>
>>> (gdb) where
>>> #0  copy_ganesha_fh (dst=0x7fe602ffd700, src=0x7fe60a825708) at
>>> export.c:66
>>> #1  0x7fe62d5f2699 in create_handle (export_pub=0x7fe60a81f290,
>>>   fh_desc=0x7fe60a825710, pub_handle=0x7fe602ffd7b0) at export.c:136
>>> #2  0x7fe631d7b7ae in cache_inode_get_keyed (key=0x7fe60a825700,
>>>   flags=, status=0x7fe602ffd82c)
>>>   at
>>> /usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_get.c:312
>>> #3  0x7fe631d771c6 in cache_inode_lookupp_impl
>>> (entry=0x7fe60a825580,
>>>   parent=0x7fe602ffd908)
>>>   at
>>> /usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_lookupp.c:110
>>>
>>> #4  0x7fe631d77883 in cache_inode_lookupp (entry=0x7fe60a825580,
>>>   parent=0x7fe602ffd908)
>>>   at
>>> /usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_lookupp.c:172
>>>
>>> #5  0x7fe631d113a8 in nfs3_readdirplus (arg=,
>>>   worker=, req=, res=0x7fe601014140)
>>>   at
>>> /usr/src/debug/nfs-ganesha-2.2.0/src/Protocols/NFS/nfs3_readdirplus.c:268
>>>
>>> #6  0x7fe631d032a8 in nfs_rpc_execute (req=0x7fe60701c2c0,
>>>   worker_data=0x7fe60100e180)
>>>   at
>>> /usr/src/debug/nfs-ganesha-2.2.0/src/MainNFSD/nfs_worker_thread.c:1268
>>> #7  0x7fe631d04dac in worker_run (ctx=0x7fe62de7da80)
>>>   at
>>> /usr/src/debug/nfs-ganesha-2.2.0/src/MainNFSD/nfs_worker_thread.c:1535
>>> #8  0x7fe631da1a89 in fridgethr_start_routine (arg=0x7fe62de7da80)
>>>   at /usr/src/debug/nfs-ganesha-2.2.0/src/support/fridgethr.c:562
>>> #9  0x7fe630045df5 in start_thread () from /lib64/libpthread.so.0
>>> #10 0x7fe62f7151ad in clone () from /lib64/libc.so.6
>>> (gdb)
>>>
>>> Thank you
>>>
>

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Crash when running ls

2016-04-10 Thread Varghese Devassy 
Soumya,

Are there any plans of adding these missing fixes into 2.2?

Varghese Devassy
v_deva...@yahoo.com

On 2016-04-10 06:40 AM, Soumya Koduri wrote:
> Hi,
>
> I had run into similar crash when cache inode entries get reaped. 
> Below patch had fixed the issue.
>
> https://review.gerrithub.io/#/c/258687/
>
> I think this patch is not merged into V2.2. Please check 
> nfs-ganesha-2.3 or current next branch packages.
>
> Thanks,
> Soumya
>
> On 04/09/2016 05:54 AM, Varghese Devassy wrote:
>> Hi,
>>
>> We have our own FSAL that runs in the following version of NFS ganesha
>> on a CentOS system. I have been trying to locate a crash for the last
>> few days but with no progress. Any help in this matter will be greatly
>> appreciated.
>>
>> # rpm -qa | grep -i ganesha
>> nfs-ganesha-2.2.0-6.el7.x86_64
>> nfs-ganesha-utils-2.2.0-6.el7.x86_64
>> nfs-ganesha-debuginfo-2.2.0-6.el7.x86_64
>> #
>>
>> # uname -a
>> Linux vcd-test1 3.10.0-327.3.1.el7.x86_64 #1 SMP Wed Dec 9 14:09:15 UTC
>> 2015 x86_64 x86_64 x86_64 GNU/Linux
>> #
>>
>> We have been having a crash when running ls -lR for a long periods of
>> time (over 1+ hours). To make the crash earlier, we reduced the inode
>> cache to 1 by introducing the following configuration parameter.
>>
>> CACHEINODE
>> {
>>   Entries_HWMark = 1;
>> }
>>
>> With this change, I am able to get the crash in two ls commands with the
>> following steps:
>> 1. mount  /mnt
>> 2. cd /mnt
>> 3. ls
>> 4. cd var
>> 5. ls (ganesha crashes)
>>
>> It seems to me that the somehow the entry obtained from the cache has
>> the wrong file handle for var directory. Because, I checked the FH in
>> debugger and it has some FH values that seems wrong.
>>
>> The problematic dir_entry is retrieved at the following line in
>> src/Protocols/NFS/nfs3_readdirplus.c
>>
>>   188 dir_entry =
>> nfs3_FhandleToCache(&(arg->arg_readdirplus3.dir),
>>   189 &(res->res_readdirplus3.status),
>>   190   );
>>
>> Here is the stack trace.
>>
>> (gdb) where
>> #0  copy_ganesha_fh (dst=0x7fe602ffd700, src=0x7fe60a825708) at 
>> export.c:66
>> #1  0x7fe62d5f2699 in create_handle (export_pub=0x7fe60a81f290,
>>   fh_desc=0x7fe60a825710, pub_handle=0x7fe602ffd7b0) at export.c:136
>> #2  0x7fe631d7b7ae in cache_inode_get_keyed (key=0x7fe60a825700,
>>   flags=, status=0x7fe602ffd82c)
>>   at
>> /usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_get.c:312
>> #3  0x7fe631d771c6 in cache_inode_lookupp_impl 
>> (entry=0x7fe60a825580,
>>   parent=0x7fe602ffd908)
>>   at
>> /usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_lookupp.c:110 
>>
>> #4  0x7fe631d77883 in cache_inode_lookupp (entry=0x7fe60a825580,
>>   parent=0x7fe602ffd908)
>>   at
>> /usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_lookupp.c:172 
>>
>> #5  0x7fe631d113a8 in nfs3_readdirplus (arg=,
>>   worker=, req=, res=0x7fe601014140)
>>   at
>> /usr/src/debug/nfs-ganesha-2.2.0/src/Protocols/NFS/nfs3_readdirplus.c:268 
>>
>> #6  0x7fe631d032a8 in nfs_rpc_execute (req=0x7fe60701c2c0,
>>   worker_data=0x7fe60100e180)
>>   at
>> /usr/src/debug/nfs-ganesha-2.2.0/src/MainNFSD/nfs_worker_thread.c:1268
>> #7  0x7fe631d04dac in worker_run (ctx=0x7fe62de7da80)
>>   at
>> /usr/src/debug/nfs-ganesha-2.2.0/src/MainNFSD/nfs_worker_thread.c:1535
>> #8  0x7fe631da1a89 in fridgethr_start_routine (arg=0x7fe62de7da80)
>>   at /usr/src/debug/nfs-ganesha-2.2.0/src/support/fridgethr.c:562
>> #9  0x7fe630045df5 in start_thread () from /lib64/libpthread.so.0
>> #10 0x7fe62f7151ad in clone () from /lib64/libc.so.6
>> (gdb)
>>
>> Thank you
>>


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

[Nfs-ganesha-devel] Crash when running ls

2016-04-08 Thread Varghese Devassy 
Hi,

We have our own FSAL that runs in the following version of NFS ganesha 
on a CentOS system. I have been trying to locate a crash for the last 
few days but with no progress. Any help in this matter will be greatly 
appreciated.

# rpm -qa | grep -i ganesha
nfs-ganesha-2.2.0-6.el7.x86_64
nfs-ganesha-utils-2.2.0-6.el7.x86_64
nfs-ganesha-debuginfo-2.2.0-6.el7.x86_64
#

# uname -a
Linux vcd-test1 3.10.0-327.3.1.el7.x86_64 #1 SMP Wed Dec 9 14:09:15 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
#

We have been having a crash when running ls -lR for a long periods of 
time (over 1+ hours). To make the crash earlier, we reduced the inode 
cache to 1 by introducing the following configuration parameter.

CACHEINODE
{
 Entries_HWMark = 1;
}

With this change, I am able to get the crash in two ls commands with the 
following steps:
1. mount  /mnt
2. cd /mnt
3. ls
4. cd var
5. ls (ganesha crashes)

It seems to me that the somehow the entry obtained from the cache has 
the wrong file handle for var directory. Because, I checked the FH in 
debugger and it has some FH values that seems wrong.

The problematic dir_entry is retrieved at the following line in 
src/Protocols/NFS/nfs3_readdirplus.c

 188 dir_entry = 
nfs3_FhandleToCache(&(arg->arg_readdirplus3.dir),
 189 &(res->res_readdirplus3.status),
 190   );

Here is the stack trace.

(gdb) where
#0  copy_ganesha_fh (dst=0x7fe602ffd700, src=0x7fe60a825708) at export.c:66
#1  0x7fe62d5f2699 in create_handle (export_pub=0x7fe60a81f290,
 fh_desc=0x7fe60a825710, pub_handle=0x7fe602ffd7b0) at export.c:136
#2  0x7fe631d7b7ae in cache_inode_get_keyed (key=0x7fe60a825700,
 flags=, status=0x7fe602ffd82c)
 at 
/usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_get.c:312
#3  0x7fe631d771c6 in cache_inode_lookupp_impl (entry=0x7fe60a825580,
 parent=0x7fe602ffd908)
 at 
/usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_lookupp.c:110
#4  0x7fe631d77883 in cache_inode_lookupp (entry=0x7fe60a825580,
 parent=0x7fe602ffd908)
 at 
/usr/src/debug/nfs-ganesha-2.2.0/src/cache_inode/cache_inode_lookupp.c:172
#5  0x7fe631d113a8 in nfs3_readdirplus (arg=,
 worker=, req=, res=0x7fe601014140)
 at 
/usr/src/debug/nfs-ganesha-2.2.0/src/Protocols/NFS/nfs3_readdirplus.c:268
#6  0x7fe631d032a8 in nfs_rpc_execute (req=0x7fe60701c2c0,
 worker_data=0x7fe60100e180)
 at 
/usr/src/debug/nfs-ganesha-2.2.0/src/MainNFSD/nfs_worker_thread.c:1268
#7  0x7fe631d04dac in worker_run (ctx=0x7fe62de7da80)
 at 
/usr/src/debug/nfs-ganesha-2.2.0/src/MainNFSD/nfs_worker_thread.c:1535
#8  0x7fe631da1a89 in fridgethr_start_routine (arg=0x7fe62de7da80)
 at /usr/src/debug/nfs-ganesha-2.2.0/src/support/fridgethr.c:562
#9  0x7fe630045df5 in start_thread () from /lib64/libpthread.so.0
#10 0x7fe62f7151ad in clone () from /lib64/libc.so.6
(gdb)

Thank you

-- 
Varghese Devassy
v_deva...@yahoo.com


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301=/ca-pub-7940484522588532
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel