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:
>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
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
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
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,
>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
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
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