Inconsistent size/units between `proj-quota-report` and `s3cmd du` after Transfer from Cheaha to LTS
@bdu-birhanu is already working on this.
Since Oct 21, 2025.
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What is inaccurate?
A user transferred data from the Cheaha project directory to LTS. After the transfer has completed, the reported size differed between the project directory and the LTS bucket.
When running the following commands:
proj-quota-report <project>for the Cheaha project directory, it shows sizes in TBs3cmd du -H s3://<bucket-name>for the LTS bucket, it shows sizes in T
In addition to the unit difference, the sizes themselves differ (21.66TB vs 20T), which leads to confusion when validating data transfers. This issue is likely due to a difference in unit representation (base-10, decimal,TB) vs (base-2 , binary, TiB).
@mdefende may add more.
Where is the inaccuracy?
https://docs.rc.uab.edu/data_management/cheaha_storage_gpfs/#how-much-space-do-i-have-left
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.