Re: [Nfs-ganesha-devel] nfs ganesha vs nfs kernel performance

2018-02-19 Thread William Allen Simpson
On 2/16/18 4:35 PM, Deepak Jagtap wrote:    There is only one client with 2 worker threads each worker thread generating 64 outstanding requests. Configured both servers (knfs & ganesha) with 128 worker threads.    I think client is fine  and is sending the request concurrently.  For knfs

Re: [Nfs-ganesha-devel] nfs ganesha vs nfs kernel performance

2018-02-19 Thread Matt Benjamin
On Fri, Feb 16, 2018 at 11:23 AM, William Allen Simpson wrote: >> > Actually, 2.6 should handle as many concurrent client requests as you like. > (Up to 250 of them.) That's one of its features. > > The client is not sending concurrent requests. This seems

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: dbus: don't call dbus_bus_release_name if dbus setup failed

2018-02-19 Thread GerritHub
>From Jeff Layton : Jeff Layton has uploaded this change for review. ( https://review.gerrithub.io/400292 Change subject: dbus: don't call dbus_bus_release_name if dbus setup failed .. dbus: don't call

[Nfs-ganesha-devel] Announce Push of V2.6.0

2018-02-19 Thread Frank Filz
Branch next Tag:V2.6.0 Release Highlights * A variety of cleanup things * Bump FSAL version * For gluster, pnfs_mds is false by default. * Fix copyrights on FSAL_MEM * move read EOF handling to fsal_read2 * NFS: fix delegation conflict check in open4_ex * dbus:

Re: [Nfs-ganesha-devel] ACL support

2018-02-19 Thread Sagar M D
Sriram, I was using nfsv4 acl commands only. [root@BDC sagar]# nfs4_getfacl 1.txt Operation to request attribute not supported. [root@BDC sagar]# nfs4_setfacl -a A::10:rxtncy 1.txt Operation to request attribute not supported. Failed to instantiate ACL. Thanks, Sagar. On Fri, Feb 16,

Re: [Nfs-ganesha-devel] READDIR doesn't return all entries.

2018-02-19 Thread William Allen Simpson
On 2/13/18 8:00 PM, Frank Filz wrote: You still don’t mention FSAL… I’m suspecting non-unique cookies from the FSAL as a cause. You may want to turn on CACHE_INODE and NFS_READDIR to FULL_DEBUG to see what is going on. A tcpdump trace won’t show anything useful (since we won’t see what cookies

Re: [Nfs-ganesha-devel] ACL support

2018-02-19 Thread Sagar M D
Sriram, Setting ATTR_ACL in supported_attrs helped. Now I could able to get the V4 ACLs. Thanks!. Frank, Currently we are doing what you are suggesting i.e we are persistently saving the in-memory representation of ganesha NFSV4 ACL on disk. And I'm not sure whether we are ready to check in our

Re: [Nfs-ganesha-devel] ls returns NOENT

2018-02-19 Thread Daniel Gryniewicz
Mdcache is working correctly here. It tried to find it in the cache, and failed. It got the write lock, and tried again, and failed. Then it called mdc_lookup_uncached(), which called into the FSAL, and got back ENOENT. So the underlying FSAL is to blame here, I believe. Daniel On

Re: [Nfs-ganesha-devel] ACL support

2018-02-19 Thread Sriram Patil
Thank you for the correction, Frank. Sagar, there are a couple of more things that you have not mentioned yet, 1. Have you set ATTR_ACL in supported_attrs field of your FSALs static fsinfo? (check usage of function nfs4_Fattr_Supported to know why this is required) 2. You may also want

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Create the LUSTRE FSAL over VFS FSAL

2018-02-19 Thread GerritHub
>From Patrice LUCAS : Patrice LUCAS has uploaded this change for review. ( https://review.gerrithub.io/400517 Change subject: Create the LUSTRE FSAL over VFS FSAL .. Create the LUSTRE FSAL over VFS FSAL