Bug 1359408
Summary: | [RGW:NFS]:- stat output for the "size" and "blocks" always shown as 0 for rgw buckets (directories) 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: | Tejas <tchandra> |
Severity: | low | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | low | ||
Version: | 2.0 | CC: | anharris, cbodley, ceph-eng-bugs, flucifre, hnallurv, kbader, kdreyer, mbenjamin, sweil, uboppana |
Target Milestone: | z1 | ||
Target Release: | 3.3 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
.NFS Ganesha does not show bucket size or number of blocks
NFS Ganesha, the NFS interface of the Ceph Object Gateway, lists buckets as directories. However, the interface always shows that the directory size and the number of blocks is `0`, even if some data is written to the buckets.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-02-03 04:26:48 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1322504, 1383917, 1412948, 1494421 |
Description
shylesh
2016-07-23 20:04:59 UTC
The RGW NFS implementation currently does not make any attempt to map bucket loading to directory size. The implementation does not attempt to calculate or estimate link counts for ordinary directories, either. Either of these might have updated behavior in 2.1, but may always have divergent behavior from ordinary NFS. RGW NFS is not expected to have fully consistent NFS semantics. We are still exploring what semantics best fit the needs of customers for NFS-S3 integration. Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri |