Bug 1392260

Summary:	gnome-settings-daemon shows false low free disk space alerts for GPFS mounts
Product:	Red Hat Enterprise Linux 7	Reporter:	amit yadav <ayadav>
Component:	gnome-settings-daemon	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	cww, mclasen, oholy, sanchezp, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	gnome-settings-daemon-3.26.1-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 12:55:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1298243, 1420851, 1479818

Description amit yadav 2016-11-07 02:36:30 UTC

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.

Comment 2 Bastien Nocera 2016-11-07 12:42:18 UTC

Same as:
https://bugzilla.gnome.org/show_bug.cgi?id=708786
for BTRFS

Comment 3 Ondrej Holy 2016-11-08 07:44:25 UTC

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

Comment 4 Ondrej Holy 2017-02-24 10:03:30 UTC

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...

Comment 5 Ondrej Holy 2017-02-24 13:59:23 UTC

See proposed patches in the upstream bug...

Comment 12 errata-xmlrpc 2018-04-10 12:55:16 UTC

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