[Nfs-ganesha-devel] Fwd: How to disable ATTR_FILEID

Hi, I wanted to disable ATTR_FILEID for my implementation. I removed it from the mask returned in fs_supported_attrs. Also, I am explicitly unsetting it in getattrs, lookup and lookup_path. But as I see on the client side, it is still honouring the value set in fileid. I am setting st_ino = 2

Re: [Nfs-ganesha-devel] Fwd: How to disable ATTR_FILEID

As currently > coded, I don't think you can disable either of them. > > Daniel > > On 08/12/2016 03:09 AM, sriram patil wrote: > > Hi, > > > > I wanted to disable ATTR_FILEID for my implementation. I removed it from > > the mask returned in fs_supported_attrs.

Re: [Nfs-ganesha-devel] Fwd: How to disable ATTR_FILEID

ll need to recode this function. > > > > Frank > > > > *From:* sriram patil [mailto:spsrirampa...@gmail.com] > *Sent:* Friday, August 12, 2016 12:09 AM > *To:* nfs-ganesha-devel@lists.sourceforge.net > *Subject:* [Nfs-ganesha-devel] Fwd: How to disable ATTR_FILEID

Re: [Nfs-ganesha-devel] Fwd: How to disable ATTR_FILEID

Great! Will get upto speed with it then . Thanks. On Mon, Aug 15, 2016, 9:53 PM Frank Filz <ffilz...@mindspring.com> wrote: > It’s not in plan by anyone actively working on Ganesha, but we always > welcome new participants in the community. > > > > Frank >

[Nfs-ganesha-devel] Why FATTR4_ARCHIVE does not have decode method?

Hi, I was trying to use NFS Ganesha NFSv4 export using a windows client. But this windows client is sending FATTR4_ARCHIVE in createattrs as part of OPEN and fails to create any file. decode method for FATTR4_ARCHIVE is not implemented, it returns NOOP. I figured that the read-only attributes do

Re: [Nfs-ganesha-devel] Why FATTR4_ARCHIVE does not have decode method?

Is there any NFSv4 Windows client that works with ganesha? Thanks, Sriram On Thu, Feb 23, 2017 at 10:57 PM, Frank Filz <ffilz...@mindspring.com> wrote: > Hmm, I don’t think Ganesha advertises support for FATTR4_ARCHIVE, so > client SHOULD NOT be sending it. > > > > Fran

Re: [Nfs-ganesha-devel] Request: I'm looking for good file system test programs

Hi Kevin, You can take a look at xfstests. It does data correctness checks as well. You will have to google for figuring out the download and build procedure. - Sriram On Tue, Jan 17, 2017 at 1:07 AM, Kevin C. wrote: > > I'm looking for file system operation/stability

Re: [Nfs-ganesha-devel] ganesha config editor user interface thoughts

Hi Malahal, Can we have the key value pairs as options to the commands? For example, ganesha_config add export path --pseudo --protocols 4 --access RW --exportid 30 This way the block can be setup in a single command. Also, one does not have to worry about the exact key and cases (like

[Nfs-ganesha-devel] Kerberos with virtual IP failovers

Hi All I have been trying to setup HA feature with VIP failovers for nfs ganesha. I have been able to successfully setup HA for sys authentication flavour. I am facing problem with GSS authentication for HA feature. I have exported my mount point krb5 and have mounted on a different machine. All

Re: [Nfs-ganesha-devel] Kerberos: Not working because response uses cached krb service from authgss_hash

request "still being processed" has been validated and unwrapped. If > that's the case, then I do suspect that any further use of the request > version of the service value is valid. > > Matt > > - Original Message - > > From: "sriram patil"

[Nfs-ganesha-devel] Consistently hitting OOM killer

Hi, We have been able to reproduce the OOM killer error consistently. NFS Ganesha memory consumption goes as high as 85-90 gigs (>60% of total memory). The test case is very simple, just keep creating files (with dd, bs=64k count=1). The setup has 1 NFS Ganesha server and 8 clients which are

[Nfs-ganesha-devel] Moving from 2.3 to 2.4

Hi, We have been working with 2.3-stable release for a while now. We have stabilised our FSAl layer recently and wanted to move to 2.4. I can see that there are a lot of design changes as well which went into 2.4. How is the FSAL layer impacted with these changes? Are there any semantic changes?

[Nfs-ganesha-devel] OP_OPEN does not seem to follow POSIX semantics in case of create

Hi, According to POSIX semantics, when open is does with O_CREAT and O_EXCL then it should return EEXIST. But, ganesha always expects fsal layer to return EEXIST from create if the file already exists. This is handled in cache_inode_create. If fsal create returns EEXIST then ganesha does a lookup

[Nfs-ganesha-devel] NLM locks recovery issue

Hi, I was looking into NLM locking code for NFSv3. According to NLM/NSM protocols specifications, when server restarts, the client should send nlm4_Lock request with "reclaim" flag set. This reclaim is honored only if "NLM server" is in grace period. However, this code in nlm4_Lock function

Re: [Nfs-ganesha-devel] NLM locks recovery issue

scripts supposed to use sm_notify.fanesha binary in some way or it is just test code? Thanks, Sriram On 16-Oct-2017 11:55 PM, "sriram patil" <spsrirampa...@gmail.com> wrote: > > > On 16-Oct-2017 12:50 PM, "Malahal Naineni" <mala...@gmail.com> wrote: >

[Nfs-ganesha-devel] Multi instance Ganesha with DBus

Hi, AFAIK we can run only single instance of nfs-ganesha on a given machine which supports dbus signals. Running with different ports, nfs ganesha service comes up, but the dbus signals work only for the first (primary) instance. We cannot interact with the ganesha instances (other than primary)

Re: [Nfs-ganesha-devel] Multi instance Ganesha with DBus

. So, all ganesha servers will register with the host dbus. This is why I need different bus names for every ganesha server running inside containers. Thanks, Sriram On 03-Oct-2017 5:35 PM, "Daniel Gryniewicz" <d...@redhat.com> wrote: > On 10/03/2017 02:31 AM, sriram p

Re: [Nfs-ganesha-devel] NLM locks recovery issue

is not in the client cache, the notify signal will be ignored, otherwise it will try to reclaim the lock. - Sriram On Tue, Oct 17, 2017 at 9:59 PM, sriram patil <spsrirampa...@gmail.com> wrote: > Ohh okay. Thanks for the help Frank and Malahal. I will look into this > further. I will update on

Re: [Nfs-ganesha-devel] NLM locks recovery issue

scripting. To be > honest, I haven’t actually looked at the various sample scripts, for > development, I run a modified init.d script from the Ganesha 1.5 timeframe… > > > > I think sm-notify –f does update the NSM state number. > > > > Frank > > > > *From:* sriram pati

Re: [Nfs-ganesha-devel] Subfsal export

niel > > On 11/08/2017 03:04 PM, Frank Filz wrote: > >> Yea, in the case of wanting to allow symlink exports, you would need to >> replace the method. I’d be interested in why you want to allow them. That >> is something that actually could be handled by a confi

Re: [Nfs-ganesha-devel] Subfsal export

and not making the implementation opensource does not violate any license terms. Thanks, Sriram On 08-Nov-2017 8:19 PM, "Daniel Gryniewicz" <d...@redhat.com> wrote: > On 11/08/2017 02:41 AM, sriram patil wrote: > >> Hi, >> >> In the subfsal framework

Re: [Nfs-ganesha-devel] Subfsal export

t; FSAL_RGW, though added in a generic way so other FSALs might use it). > > Frank > > > Daniel > > > > On 11/08/2017 10:51 AM, sriram patil wrote: > > > Yes, I am making a new sub fsal. May not push it to upstream because > > > it will not be us

Re: [Nfs-ganesha-devel] Subfsal export

"sub fsal". For bypassing some part of the underlying fsal function, is rewriting the function the only way? Thanks, Sriram On Wed, Nov 8, 2017 at 11:22 PM, sriram patil <spsrirampa...@gmail.com> wrote: > Hmm stackable FSAL sounds like a good option. Let me investigate on that. &

Re: [Nfs-ganesha-devel] [FSAL_VFS] Probable memory leak when deallocating handles

of having a separate cache in sub fsal. Thanks, Sriram On Mon, Jan 8, 2018 at 11:58 AM, sriram patil <spsrirampa...@gmail.com> wrote: > Hi, > > I was going through the vfs_fsal_obj_handle workflow. As part of the > function alloc_handle we allocate the handle with the help of >

[Nfs-ganesha-devel] Weekly meeting link

Hi, Can anyone share the weekly meeting link? I tried the link from github wiki few weeks back and it did not work for some reason. Also, as far as I know the weekly meeting timings are 10PM IST every Tuesday. Please let me know if there is any change in that as well. Thanks, Sriram

[Nfs-ganesha-devel] [FSAL_VFS] Probable memory leak when deallocating handles

Hi, I was going through the vfs_fsal_obj_handle workflow. As part of the function alloc_handle we allocate the handle with the help of vfs_sub_alloc_handle. vfs_sub_alloc_handle allocates vfs_fsal_obj_handle and vfs_file_handle_t back to back. And when releasing the handle (obj_ops->release), it

Re: [Nfs-ganesha-devel] [FSAL_VFS] Probable memory leak when deallocating handles

e handles from being evicted so they don’t have to do additional > caching work…). > > > > Frank > > > > *From:* sriram patil [mailto:spsrirampa...@gmail.com] > *Sent:* Sunday, January 7, 2018 11:00 PM > *To:* nfs-ganesha-devel@lists.sourceforge.net > *Cc:* k

Re: [Nfs-ganesha-devel] [FSAL_VFS] NFSv4 referrals not working

Yes, the fix looks straight forward. Let me work on it, will submit the review soon. Thanks, Sriram From: Frank Filz <ffilz...@mindspring.com> Date: Wednesday, January 17, 2018 at 8:24 PM To: Sriram Patil <srir...@vmware.com>, "nfs-ganesha-devel@lists.sourceforge.net&quo

[Nfs-ganesha-devel] [FSAL_VFS] NFSv4 referrals not working

Hi, I was experimenting with NFSv4 referrals recently and I have not been able to get it working. I tried this on stable version 2.5, so it has referrals changes in VFS code. Here’s what I did, Server A: Path=/A/real/path; Pseudo=/A/pseudo/path Server B: Path=/B/real/path;

[Nfs-ganesha-devel] [GlusterFS] NFsv4 to POSIX ACL conversion

Hi, I see that there is NFSv4 ACLs to POSIX ACLs mapping code written in GlusterFS FSAL. Since, this is pretty standard code and other FSAls may use it instead of duplicating the same code every time, can we move the ACL conversion code to a common place in Ganesha? The code is independent of

Re: [Nfs-ganesha-devel] About referrals in FSAL_VFS

-utils package? Is it just a package dependency or something else? Thanks, Sriram From: Frank Filz <ffilz...@mindspring.com> Date: Thursday, February 8, 2018 at 8:34 PM To: Sriram Patil <srir...@vmware.com>, "nfs-ganesha-devel@lists.sourceforge.net" <nfs-ganesha-de

Re: [Nfs-ganesha-devel] About referrals in FSAL_VFS

ebruary 8, 2018 at 12:24 AM To: Sriram Patil <srir...@vmware.com>, "nfs-ganesha-devel@lists.sourceforge.net" <nfs-ganesha-devel@lists.sourceforge.net> Subject: RE: [Nfs-ganesha-devel] About referrals in FSAL_VFS If you could share the details of what you want to do different

Re: [Nfs-ganesha-devel] About referrals in FSAL_VFS

for them. This should also allow a way to follow the default VFS mechanism Thanks, Sriram From: Frank Filz <ffilz...@mindspring.com> Date: Friday, February 9, 2018 at 12:05 AM To: Sriram Patil <srir...@vmware.com>, "nfs-ganesha-devel@lists.sourceforge.net&quo

Re: [Nfs-ganesha-devel] New things in feature board

Hi Supriti, The link you have provided is not working. And the 2.7 board seems to be closed. I checked things here - https://github.com/nfs-ganesha/nfs-ganesha/projects. Am I missing something? Thanks, Sriram From: Supriti Singh Date: Thursday, February 8, 2018 at

[Nfs-ganesha-devel] About referrals in FSAL_VFS

Hi, I understand that we are not supposed to extend subfsals and should move to Stackable FSALs. But, since it is not possible in some cases (e.g. open_by_handle is not supported by the kernel), subfsal has to stay. Currently, the referrals decision is made by FSAL_VFS depending on a specific

[Nfs-ganesha-devel] pynfs fslocations tests failure

Hi, I was testing the pynfs fslocations tests on latest code base with VFS mounts on ext4 and have found that most of the tests fail. Are these known issues? Please find the command and the output below > showmount –e Export list for localhost.localdomain: /exports/default (everyone)

Re: [Nfs-ganesha-devel] ACL support

Hi Sagar, I see in your conf file that you are using NFSv4. POSIX acls do not work on NFSv4. NFSv4 acls are a superset of POSIX acls. For using NFSv4 acls you need to use nfs4_getfacl and nfs4_setfacl commands from the client. You can find these commands in nfs4-acl-tools package. - Sriram

Re: [Nfs-ganesha-devel] ACL support

to take a look at ENABLE_RFC_ACL flag. This is not for enabling ACLs but it is used for access checks in fsal_check_access_acl. - Sriram From: Frank Filz <ffilz...@mindspring.com> Date: Friday, February 16, 2018 at 8:19 PM To: Sriram Patil <srir...@vmware.com>, 'Sagar M D' <sag

[Nfs-ganesha-devel] pynfs WRT14 failure with timeout

Hi, I have been continuously seeing this issue when running pynfs test suite WRT14st_write.testLargeWrite : RUNNING Traceback (most recent call last): File "/root/pynfs/nfs4.0/lib/testmod.py", line 222, in run self.runtest(self, environment) File

Re: [Nfs-ganesha-devel] About referrals in FSAL_VFS

. Is ti okay to get rid of the fs_locations callback or should I just add a comment mentioning this will be deprecated? It will also require changes in the existing FSALs which use the fs_locations callback currently. What do you think? Thanks, Sriram From: Sriram Patil <srir...@vmware.com>

Re: [Nfs-ganesha-devel] About referrals in FSAL_VFS

ntly. What do you think? > > > > Thanks, > > Sriram > > > > *From: *Sriram Patil <srir...@vmware.com> > *Date: *Saturday, March 10, 2018 at 8:30 PM > *To: *Frank Filz <ffilz...@mindspring.com>, " > nfs-ganesha-devel@lists.sourceforge.net&quo

Re: [Nfs-ganesha-devel] About referrals in FSAL_VFS

Okay, sounds good. Will work towards getting this right. Thanks, Sriram From: Frank Filz <ffilz...@mindspring.com> Date: Friday, March 9, 2018 at 11:20 PM To: Sriram Patil <srir...@vmware.com>, "nfs-ganesha-devel@lists.sourceforge.net" <nfs-ganesha-devel@lists.sou

Re: [Nfs-ganesha-devel] About referrals in FSAL_VFS

ing and retrieving the fslocation details as discussed before. Let me know if this looks like a good thing to do or should we think about fslocations in attrlist? Thanks, Sriram From: Sriram Patil <srir...@vmware.com> Date: Friday, February 9, 2018 at 10:30 AM To: Frank Filz <ffilz...@mi

[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] is_superuser fsal export API

Thanks for the clarification, Frank. From: Frank Filz <ffilz...@mindspring.com> Date: Tuesday, April 10, 2018 at 10:32 PM To: Sriram Patil <srir...@vmware.com>, "nfs-ganesha-devel@lists.sourceforge.net" <nfs-ganesha-devel@lists.sourceforge.net> Subject: RE: [Nfs-gane

[Nfs-ganesha-devel] NFSv4 recovery directory path

Hi, Currently the NFSv4 recovery directory root path is as good as hard coded because it depends on the CMAKE_INSTALL_PREFIX. It is can be found in config.h after running cmake. I tried specifying a –DNFS_V4_RECOV_ROOT= when compiling, but it does not work because config.h overwrites the

Re: [Nfs-ganesha-devel] libntirpc not available anymore?

bntirpc. > It should have the latest commit needed, so "git submodule update –init > –recursive” should pass as long as you fetch the remote. > > Regards, Malahal. > > On Mon, Mar 4, 2019 at 1:07 AM Sriram Patil via Nfs-ganesha-devel > <

[Nfs-ganesha-devel] libntirpc not available anymore?

This list has been deprecated. Please subscribe to the new devel list at lists.nfs-ganesha.org.Hi, I pulled in the latest ganesha code and tried to pull ntirpc with “git submodule update –init –recursive”. It is throwing following error, Cloning into 'src/libntirpc'... Username for

Re: [Nfs-ganesha-devel] DSESS9002 and DSESS9003 test cases result in NFS4ERR_GRACE

with that field when Grace expires, so it's possible it hangs around... Daniel On 8/10/19 12:32 PM, Sriram Patil via Nfs-ganesha-devel wrote: > This list has been deprecated. Please subscribe to the new devel list at > lists.nfs-ganesha.org. > > > Hi, > > Was this fixed in some chang