Re: [Nfs-ganesha-devel] is_superuser fsal export API

Thanks for the clarification, Frank. From: Frank Filz Date: Tuesday, April 10, 2018 at 10:32 PM To: Sriram Patil , "nfs-ganesha-devel@lists.sourceforge.net" Subject: RE: [Nfs-ganesha-devel] is_superuser fsal

Re: [Nfs-ganesha-devel] Couple of stat issues.

On 4/10/18 8:49 PM, Pradeep wrote: 2. In nfs_rpc_execute(), the queue_wait is set to the difference between op_ctx->start_time and reqdata->time_queued. But reqdata->time_queued is never set (in the old code - pre 2.6-dev5, nfs_rpc_enqueue_req() used to set it; now only 9P code sets it). Is

[Nfs-ganesha-devel] Couple of stat issues.

Hello, These are couple of statistics related issues I noticed: 1. NFS4 compounds are incremented multiple times: For individual OPs, ganesha takes this path: server_stats_nfsv4_op_done() -> record_nfsv4_op() -> record_op(>compounds..) Once the compound is complete, we take another path

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: FSAL_CEPH: remove unneeded initializing variable

>From Jeff Layton : Jeff Layton has uploaded this change for review. ( https://review.gerrithub.io/407195 Change subject: FSAL_CEPH: remove unneeded initializing variable .. FSAL_CEPH: remove unneeded

[Nfs-ganesha-devel] is_superuser fsal export API

Hi, This is in reference to the discussion we had on the concall. We were experimenting with the is_superuser API call to allow a user other than the root to act as super user. This API call is not used by any of the FSALs currently. When using FSAL VFS, we found out that this mechanism works

Re: [Nfs-ganesha-devel] Ganesh 2.3 : NFSv4 client gets error NFS4ERR_OLD_STATEID

On Mon, 2018-04-09 at 10:26 -0400, Daniel Gryniewicz wrote: > So, NFS4ERR_OLD_STATEID can only happen in one circumstance: when the > State presented by the client doesn't match the State that Ganesha > expects. In this case, it's the sequence number that's off-by-one. > This could be the