Seeing "ENOENT" under "/SINGLE/DATA/ERROR/logical info" #6
Description
I ran btdu against my btrfs partition mouted as read-only and saw the following. Tried defragment, no help.
btdu v0.3.0 @ /mnt [PAUSED]
--- /SINGLE/DATA/ERROR/logical ino ------------------------------------------------------------------------------------------------------------------------------------------------------------
~116.9 GiB [100.0% ##########] ENOENT
--- Details: ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- Average query duration: 0.0000153 seconds
- Represented size: ~116.9 GiB (123783 samples)
- Logical offsets: ..., 1004368585530, 178054220006, 421607607093
--- Explanation:
An error occurred while trying to look up which inodes use a particular logical offset.
Children of this node indicate the encountered error code, and may have a more detailed explanation attached.
btdu v0.3.0 @ /mnt [PAUSED]
--- INFO: /SINGLE/DATA/ERROR/logical ino/ENOENT -----------------------------------------------------------------------------------------------------------------------------------------------
--- Details:
- Error code: 2
- Error message: No such file or directory
- Average query duration: 0.0000153 seconds
- Represented size: ~116.9 GiB (123783 samples)
- Logical offsets: ..., 1004368585530, 178054220006, 421607607093
--- Explanation:
btrfs reports that there is nothing at the random sample location that btdu picked.
This most likely represents allocated but unused space, which could be reduced by running a balance on the DATA block grp.
Could anyone help
- What does the error mean? Or what documents/manuals should I check?
- What should I do with the error?
- Do I really need to run balance even there is only one device to recover the space?
Thanks in advance.