Bug 1359403
| Summary: | [RGW-NFS]:- objects created from s3 apis are not visible from nfs mount point | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | shylesh <shmohan> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | Ramakrishnan Periyasamy <rperiyas> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | cbodley, ceph-eng-bugs, flucifre, hnallurv, kbader, kdreyer, mbenjamin, owasserm, rperiyas, sweil, tserlin, uboppana |
| Target Milestone: | rc | ||
| Target Release: | 2.2 | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-10.2.5-11.el7cp, nfs-ganesha-2.4.2-3.el7cp Ubuntu: ceph_10.2.5-5redhat1xenial, nfs-ganesha_2.4.2-3redhat1xenial | Doc Type: | Known Issue |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-14 15:44:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
shylesh
2016-07-23 19:01:21 UTC
This behavior is likely not a bug, or may not be a bug, depending on more detailed semantic requirements discussion. In other words, these are topics for discussion for 2.1. This feature is, as well, tech preview in 2.0--so moving to 2.1, as well. Observed this problem during 2.1 testing. buckets created in NFS mount are listed by rgw s3 api but objects created by rgw s3 api is not listed in NFS mount. Ok, this is a defect related to lack of a mechanism to efficiently expire cached directory information, on the librgw side, and lack of a dirent expiry mechanism in nfs-ganesha. nfs-ganesha has an attribute expiration mechanism which I expected to allow eventual aging out of cached dirents, but this is not the case. I don't think this behavior will be correctable with nfs-ganesha 2.4.1/2, but will be addressed with new dirent-caching changes currently being developed. That suggests we won't be able to fix this issue in 2.3. We might need a release note for 2.2. @Uday, Could you please let us know the decision of PM w.r.t the proposal made in comment 4? My proposed implementation of this feature has been pushed as: https://github.com/ceph/ceph/pull/13038 (ceph) and https://github.com/linuxbox2/nfs-ganesha/tree/next-rgw-up (nfs-ganesha) The latter must go through upstream review, sequenced after merge of the ceph change, and probably after at least one upstream bugfix related to synchronous invalidate upcall arguments (details on nfs-ganesha-devel mailing list). Matt Not seeing the buckets created by s3 in NFS mount by default but after restarting NFS service & re-mounting nfs mounts on each clients, buckets and objects created by s3 are visible. Version: Ceph: 10.2.5-7.el7cp (59e9fee4a935fdd2bc8197e07596dc4313c410a3) NFS: nfs-ganesha-rgw-2.4.1-3.el7cp.x86_64 I also observed that objects deleted from s3 are not reflected on nfs mounts and hence objects reappears again upon sending lookups on the object and also operations like write,read succeeds . Please see my remarks and candidate code in comment 9. Objects created in S3 are visible in NFS mount. sometimes max it took a minute to reflect the objects created using s3. Moving this bug to verified state. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0514.html |