SES4: Deleting files within a Rados Block Device does not free up space on the cluster.
This document (7022066) is provided subject to the disclaimer at the end of this document.
- If the goal is to free up space, so osd's are not marked as full, then it may be best to add more disks to the cluster.
- If space is available, create a new rbd device and copy the data to the new device, then delete the original rbd device. Deleting the rbd device will return the space to SES.
- In some cases "fstrim" can return the "freed" space back to SES, assuming that the stack, filesystem, drivers, kernel, HBA, and hard drives support the functionality. fstrim should be run on the filesystem within the rbd block device.
List block devices:rbd list PooNameMap the image to a new block device.rbd map --pool PoolName ImageNameList all mapped devices:rbd showmappedMount the device:mount /dev/rbd0 /mntrun fstrim:fstrim /mnt
- Mounting the file system with "-o discard" could provide same results with out having to run "fstrim".
Example: mount -o discard /dev/rbd0 /mnt
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7022066
- Creation Date: 11-Oct-2017
- Modified Date:03-Mar-2020
- SUSE Enterprise Storage
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com