Lionel Cons

@gisburn @kofemann Could you please have a look? I think nfs-ganesha is missing the "virtual hole" at the end, right?

Ganesha config file for testing. This uses intentionally user@domain+group@domain with AUTH_SYS for testing, and a custom NFSv4.1 port ``` $ cat /etc/ganesha/ganesha.conf NFS_Core_Param { # NFSv4 only (disables v2/v3 and...

@ffilz Could you please have a look?

> https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1226555 - patch submitted The patch does not work, with the config from https://github.com/nfs-ganesha/nfs-ganesha/issues/1346#issuecomment-3532030714 the group names (mygroup@MYDOMAIN) are empty.

> > https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1226555 - patch submitted > > The patch does not work, with the config from [#1346 (comment)](https://github.com/nfs-ganesha/nfs-ganesha/issues/1346#issuecomment-3532030714) the group names (mygroup@MYDOMAIN) are empty. This was not precise: The...

> We do have a partial implementation. Unfortunately much of the code we have was done before the RFC stabilized. > > I think SEEK, ALLOCATE, and DEALLOCATE are all...

> > We do have a partial implementation. Unfortunately much of the code we have was done before the RFC stabilized. > > I think SEEK, ALLOCATE, and DEALLOCATE are...

I think this fails because it is one of the first attributes which uses word[2] field in the getattr attribute field, and ganesha chokes on that.

> The current Ganesha code base does not support the FATTR4_OFFLINE attribute. This bug is NOT about FATTR4_OFFLINE attribute support. This bug is about that ANY GETATTR which contains this...

FYI the attribute "enhancement" is WRONG. This is bug which prevents any Ganesha usage because GETATTR does not follow the RFC spec for unsupported attributes.