If you are not using open2, then file creation could easily be wonky. Also note
that the non-support_ex functionality is being deprecated so your FSAL would
need to be converted to support_ex if you wish to migrate to newer Ganesha (and
there will be lots of reasons to migrate to V2.6 and later as we move forward).
Frank
From: Sagar M D [mailto:sagar...@gmail.com]
Sent: Sunday, February 11, 2018 6:27 AM
To: d...@redhat.com
Cc: nfs-ganesha-devel@lists.sourceforge.net
Subject: Re: [Nfs-ganesha-devel] owner and group issue.
Daniel,
We are using open call not open2 call. But i verified our FSAL is returning
correct owner and group id for getattr call right after file gets created.
And it is intermittent issue and can be reproduced easily. This is happening
basically during process starts.
Thanks,
Sagar.
On Thu, Feb 8, 2018 at 10:30 PM, Daniel Gryniewicz <d...@redhat.com
<mailto:d...@redhat.com> > wrote:
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 because after 60 seconds, the attribute cache expires, and so
the next getattr refreshes the cache, fixing the issue.
Is your FSAL correctly returning the attributes in attrs_out in it's open2()
call?
Daniel
On 02/08/2018 05:15 AM, Sagar M D wrote:
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 correct owner and group. But ls -ltr is
showing -2. If i try after few mins all works fine.
[root@BDC testPerm]# touch 4.txt
[root@BDC testPerm]# ls -ltr
total 0
-rw-r--r--. 1 root root 0 Feb 7 20:10 1.txt
-rw-r--r--. 1 root root 0 Feb 7 20:17 2.txt
-rw-r--r--. 1 root root 0 Feb 7 20:17 3.txt
-rw-r--r--. 1 4294967294 4294967294 0 Feb 7 20:21 4.txt
ls tried after some time:-
[root@BDC testPerm]# touch 5.txt
[root@BDC testPerm]# ls -ltr
total 0
-rw-r--r--. 1 root root 0 Feb 7 20:10 1.txt
-rw-r--r--. 1 root root 0 Feb 7 20:17 2.txt
-rw-r--r--. 1 root root 0 Feb 7 20:17 3.txt
-rw-r--r--. 1 root root 0 Feb 7 20:21 4.txt
-rw-r--r--. 1 root root 0 Feb 7 20:33 5.txt
is there any known issues ? Are we missing anything from our side?
Thanks,
Sagar.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
<mailto:Nfs-ganesha-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
<mailto:Nfs-ganesha-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
