Here's for GPFS and CEPH.
https://review.gerrithub.io/357080
Daniel
On 04/13/2017 09:16 AM, Soumya Koduri wrote:
>
>
> On 04/13/2017 06:33 PM, Daniel Gryniewicz wrote:
>> I was seeing this on FSAL_MEM too, and thanks for pointing out the
>> cause. It was because I wasn't setting attrs.support
On 04/13/2017 06:33 PM, Daniel Gryniewicz wrote:
> I was seeing this on FSAL_MEM too, and thanks for pointing out the
> cause. It was because I wasn't setting attrs.supported (only
> attrs.valid_mask) so required attributes were not supported. I've
> updated FSAL_MEM, and will try to generate a
I was seeing this on FSAL_MEM too, and thanks for pointing out the
cause. It was because I wasn't setting attrs.supported (only
attrs.valid_mask) so required attributes were not supported. I've
updated FSAL_MEM, and will try to generate a patch for other FSALs.
Daniel
On 04/13/2017 06:38 AM,
I see this issue even on GlusterFS. That seem to be the reason behind
https://ci.centos.org//job/nfs_ganesha_cthon04/563/console test failure
since this commit got merged.
NFSv3 mounts are working fine, but the v4 mounts are unsuccessful. I do
not see any errors in the pkt trace. Will enable deb
Hmm, it may be some issue with what attribute support is claimed.
I would start with a tcpdump trace and see if you can determine which actual
operation is failing.
Turning on FSAL debugging might help.
Frank
> -Original Message-
> From: Swen Schillig [mailto:s...@vnet.ibm.com]
> Sent:
Hi Frank
while testing some of my patches I figured your commit
65599c645a81edbe8b953cc29ac29978671a11be
broke the ability to mount V4 filesystems on GPFS (ERR_ACCESS).
Haven't had time to look into it yet,
Hopefully you already have a good idea what it could be.
Otherwise I will look into it
