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

Okay, so there are a bunch of things that we need to do. I will just list them down here, let me know if I miss anything. 1. Fs locations can be moved to attrlist and FSAL can fill it as part of getattr if required 2. We need ref counting for fs locations for handling attr copy where

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Add debug surrounding FSAL module refcounting

>From Frank Filz : Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/399077 Change subject: Add debug surrounding FSAL module refcounting .. Add debug surrounding FSAL

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Don't double stack MDCACHE on FSAL_PSEUDO exports

>From Frank Filz : Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/399078 Change subject: Don't double stack MDCACHE on FSAL_PSEUDO exports .. Don't double stack MDCACHE

[Nfs-ganesha-devel] Using root privileges when using kerberos exports with Ganesha.

Hello, It looks like Ganesha converts certain principals to UID/GID 0 (idmapper.c:principal2uid()). I noticed that when a client uses kerberos with AD, the default principal is @. So when NFS operations are tried with root on client, it sends the principal in @ format which will not be mapped to

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: MDCACHE - Don't ref PSEUDO when stacking

>From Daniel Gryniewicz : Daniel Gryniewicz has uploaded this change for review. ( https://review.gerrithub.io/398977 Change subject: MDCACHE - Don't ref PSEUDO when stacking .. MDCACHE - Don't ref PSEUDO

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pullup ntirpc 1.6.1

>From Daniel Gryniewicz : Daniel Gryniewicz has uploaded this change for review. ( https://review.gerrithub.io/398978 Change subject: Pullup ntirpc 1.6.1 .. Pullup ntirpc 1.6.1 Change-Id:

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

There are places the struct attrlist gets copied, if so, either the referral needs to be duplicated in that copy, or it needs to be a single entity with a refcount. One advantage of adding the referral to the struct attrlist is that MDCACHE will manage cache life of it. It may or may not

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

attrlist changes sound good. I am trying to figure out the necessity of a separate cache and ref counts. As far as I see, there will not be multiple references to fs_locations (which will be just a string in attrlist). What do you mean by xattr utility is being added in nfs-utils? Is that

Re: [Nfs-ganesha-devel] owner and group issue.

This is not a known issue, as far as I'm aware. I'm assuming you never changed 4.txt at all, it just fixed itself on it's own? This means, to me, that the correct value is being set on the file, but an incorrect one is returned to the user. That's a getattr() issue, and it resolves itself

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

We will actually need to add everyone who is interested to the organization anyway, otherwise we can’t assign them issues… Problems with how issues were assigned was actually one of the reasons we tried to migrate to Bugzilla and not use issues. But with this, we just need to bite the bullet

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

Ok, the additional sub_fsal ops look workable. For the protocol layer stuff, we need a quick way to check if an object is a junction. One option is to resurrect the fsal_obj_handle JUNCTION type. Another option is to add fs_locations to struct attrlist and then an FSAL supporting referral

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

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

Hi Sriram, Earlier we had boards at the repo level (https://github.com/nfs-ganesha/nfs-ganesha/projects), but there were some permission issues, and it could be viewed by everyone but not all can add cards. So we moved the board to organization level. But sadly, according to this

[Nfs-ganesha-devel] owner and group issue.

Hi, We are using nfs-ganesha 2.5 for our fsal, I see sometimes created file have -2 has owner and group even though root is created the file and no_root_squash is enabled. I see this behavior for only for short duration that to right after ganesha restarts. During file creation, our fsal gets

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

Hello all, I am trying new things in our project board. Let me know if the approach is okay, or you would like to change something. 1. Adding issues in github: It seems like only when there is an issue, I can assign it to the developer actively working on it. For example, in 2.7 board I