There has been some confusion in #101 over the plan to replace disk-usage-analyzer and baobab with gnome-usage. Let's use this ticket to get on the same page and track progress.
We were planning on replacing disk-usage-analyzer and baobab with a new Usage app, and an initial implementation was written a while back
Since then, two things have happened:
As far as I understand it, we are currently waiting for @hergertme to get back to this, while simultaneously exploring what the future might be for disk usage. There's some relevant upstream discussion here.
Two relevant concepts:
Shared extents can exist on XFS and Btrfs, and are created by reflink copies. This is soon to be the default for cp. And reflinks are created by podman (and mobi/docker) used for container support. Shared extents are also created by Btrfs snapshots and deduplication.
Shared extents and compression thwart big picture accuracy with du reporting, leading to du overestimating space consumption. It reports only the uncompressed view of a directory, and will report shared extents as if they're exclusive to the enclosing directory. It's correct behavior from a narrow point of view, but misleading from a zoomed out perspective. So I think both will need to be accounted for, or it'll lead to unexpected outcomes.
du
Is it fair to say this is in-scope for Fedora 34 (or Future release), and not Fedora 33? If not feel free to flip the milestone as appropriate.
Metadata Update from @chrismurphy: - Issue set to the milestone: Fedora 34
This issue is mostly to track ongoing developments in this area and I don't think we have a specific target in mind, so setting it as future release.
Metadata Update from @aday: - Issue set to the milestone: Future Release (was: Fedora 34)
Metadata Update from @catanzaro: - Issue tagged with: default-apps
Upstream plans in https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/145 have changed: gnome-usage has just not worked out, while baobab has been improved considerably. Let's close this.
Metadata Update from @catanzaro: - Issue close_status updated to: Won't fix - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.