Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
gnome-settings-daemon shows false low free space alerts for GPFS mounts with very large disk space. The alert shows up intermittently since it requires a GPFS filesystem to become fairly full.
Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.14.4-9.el7.x86_64
How reproducible:
Frequently
Additional info:
Previously customer has reported this issue on RHEL6. A bug (https://bugzilla.redhat.com/show_bug.cgi?id=1253770) was filed and closed due to inactivity from customer's end.
I wonder why do you think this is GVfs issue. AFAIK settings-daemon uses GUnixMountMonitor, which is implemented in GLib/GIO, and free space is based on statvfs output. So, GVfs is not involved at all. Similar for the upstream issue, see:
https://bugzilla.gnome.org/show_bug.cgi?id=708786#c23
I do think that g-s-d should check free space per device path and not per mount path. Similarly for g-c-c. This should fix the multiple warnings issue and wrong total size info at least for some filesystem types (i.e. BTRFS). I have no idea, how GPFS works and what is wrong with it, because the bug report is pretty brief, but we can probably ignore such obscure filesystem types in g-s-d / g-c-c if the previous suggestion doesn't help...
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0770