Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Red Hat Customer
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 1710155
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh92 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1710155
-
libcephfs readdir call go in recursive and fail to return dir entries
Summary:
libcephfs readdir call go in recursive and fail to return dir entries
Keywords
:
Status
:
CLOSED NOTABUG
Alias:
None
Product:
Red Hat Ceph Storage
Classification:
Red Hat Storage
Component:
CephFS
Sub Component:
---
Version:
3.2
Hardware:
x86_64
OS:
Linux
Priority:
high
Severity:
high
Target Milestone:
rc
Target Release
:
3.3
Assignee:
Jeff Layton
QA Contact:
ceph-qe-bugs
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+
depends on
/
blocked
Reported:
2019-05-15 02:29 UTC by
Prashant Dhange
Modified:
2021-08-27 22:46 UTC (
History
)
CC List:
6 users
(
show
)
ceph-eng-bugs
jiazhang
jinjli
jlayton
pdonnell
sweil
Fixed In Version:
Doc Type:
If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
2019-05-16 10:03:40 UTC
Embargoed:
Dependent Products:
Red Hat OpenShift Container Storage
Red Hat OpenShift Data Foundation
Red Hat OpenStack
Flags:
pdhange
: automate_bug?
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Bugzilla
1705792
0
high
CLOSED
ls command taking too much time on nfs-ganesha mount path directory having 800 inodes and exits with "memory exhausted" ...
2022-08-11 08:32:33 UTC
Red Hat Issue Tracker
RHCEPH-1106
0
None
None
None
2021-08-27 22:46:39 UTC
Note
You need to
log in
before you can comment on or make changes to this bug.