Actions
Bug #64479
closedMemory leak detected when accessing a CephFS volume from Samba using libcephfs
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Performance/Resource Usage
Target version:
% Done:
0%
Source:
Backport:
quincy,reef,squid
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
libcephfs
Labels (FS):
Pull request ID:
Tags (freeform):
backport_processed
Merge Commit:
Fixed In:
v19.3.0-329-g55ac8d6d0b
Released In:
v20.2.0~3431
Upkeep Timestamp:
2025-11-01T01:27:01+00:00
Description
When files are continuously created and deleted from a CephFS volume accessed through Samba with libcephfs (Samba's vfs_ceph module), a steady increase of used memory is observed. The growth is relatively slow but constant and eventually it triggers the OOM killer.
The test I used to reproduce it was:
- while true; do dd if=/dev/zero of=/mnt/samba/file bs=4k count=1 status=none; rm -f /mnt/samba/file; done
This can be run in parallel using different files to make the leak to happen faster.
Updated by Venky Shankar about 2 years ago
- Category set to Performance/Resource Usage
- Status changed from New to Fix Under Review
- Assignee set to Xavi Hernandez
- Target version set to v19.0.0
- Backport set to quincy, reef
- Pull request ID set to 55619
Updated by Venky Shankar about 2 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from quincy, reef to quincy,reef,squid
Updated by Upkeep Bot about 2 years ago
- Copied to Backport #64736: quincy: Memory leak detected when accessing a CephFS volume from Samba using libcephfs added
Updated by Upkeep Bot about 2 years ago
- Copied to Backport #64737: reef: Memory leak detected when accessing a CephFS volume from Samba using libcephfs added
Updated by Upkeep Bot about 2 years ago
- Copied to Backport #64738: squid: Memory leak detected when accessing a CephFS volume from Samba using libcephfs added
Updated by Upkeep Bot about 1 year ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Upkeep Bot about 1 year ago
- Tags (freeform) set to backport_processed
Updated by Upkeep Bot 9 months ago
- Merge Commit set to 55ac8d6d0bfa7604d66218eeb3a1b7fd404e22fd
- Fixed In set to v19.3.0-329-g55ac8d6d0bf
- Upkeep Timestamp set to 2025-07-02T03:41:41+00:00
Updated by Upkeep Bot 8 months ago
- Fixed In changed from v19.3.0-329-g55ac8d6d0bf to v19.3.0-329-g55ac8d6d0b
- Upkeep Timestamp changed from 2025-07-02T03:41:41+00:00 to 2025-07-14T16:45:27+00:00
Updated by Upkeep Bot 5 months ago
- Released In set to v20.2.0~3431
- Upkeep Timestamp changed from 2025-07-14T16:45:27+00:00 to 2025-11-01T01:27:01+00:00
Actions