Public bug reported:
When scanning dirs with sparse files, the full file size is used in
computing Usage % (in the table) and also for calculating the ring size.
Curiously wherever a file size is mentioned (in table or highlighting a
ring piece) the dirs allocated size is displayed (same as what `du -hs`
would show).
This leads to weird behavior where dirs with similar reported size (in
both baobob and du) have wildly different Usage% and ring size if some
contain sparse files. It is inconsistent (either both should be
allocated size or both be file size), but to match `du` I would argue
that allocated size should be used.
I glanced at the code and I think the simple fix would be to change the
percent calculation in baobab-scanner.vala from using size to using
alloc_size. Likewise in the calculation for charts.
** Affects: baobab (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530512
Title:
Sparse files cause malproportioned charts and "usage" reporting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1530512/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
