-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
disk usage percent fix #211
Conversation
This pull request has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/omero-web-reports-disk-usage-incorrectly/42219/2 |
On merge-ci, this seems to be okay (?) Although how many TB do we have for our peruse there ? Edit: thinking about it a bit more, unless I count in some docker magic, it is sheerly not porrible that there are more than one TB of data on merge-ci ? cc @joshmoore @sbesson explained that the number is plausible, see screenshot below (only the usage of the |
|
Thanks @joshmoore - the numbers in #211 (comment) seem to match more what I would expect from the top of my head. Is the discrepancy between the web report (supported by @sbesson ) and the numbers in #211 (comment) caused by in-place imports ? And if yes, then actually, what is it that web reports there ? What is the "disk usage" of in-place imported data ? Possibly web does not take the in-place quality of the files into account ? |
Confirmed separately. Free size comes from |
The web UI reports |
Certainly no objections for this PR: taking in-place into account is going to require server-side changes. 👍 |
As a minor doc RFE, is there some place in the client UI where the caveat about the in-place imports could be mentioned? |
Agree with @sbesson about the explanation/warning in the UI. Could an additional line under "Drive space usage" saying do the job ? |
See https://forum.image.sc/t/omero-web-reports-disk-usage-incorrectly/42219
This rounds the usagePercent value before casting it to Int, to avoid strange JavaScript parseInt behaviour of ignoring exponentials for very small numbers (see example in link above).
To test: - probably not so easy to create multi-petabyte free disk space.
So might have to just check the code change against the examples in the link above.