After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674916 - Low disk space warning reports twice for separately mounted btrfs sub-volumes on the same storage pools, even when one is mounted inside of the other.
Low disk space warning reports twice for separately mounted btrfs sub-volumes...
Status: RESOLVED DUPLICATE of bug 708786
Product: gnome-settings-daemon
Classification: Core
Component: plugins
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2012-04-27 01:30 UTC by Shawn Landden
Modified: 2014-12-12 08:18 UTC
See Also:
GNOME target: ---
GNOME version: 3.3/3.4


Description Shawn Landden 2012-04-27 01:30:12 UTC 
we need some awareness of the concept of btrfs sub-volumes.

Variations of behavior:

#1.* Ask twice for same low disk situation. Do disk space analysis on analyzed filesystem only. Show/analyze files that are inaccessable because of having been mounted over (is this possible without root, do we try our best if the same subvolume is mounted in more than one places?) or just stop at these boundaries?

#2 part a: If btrfs subvolumes are nested, only ask one, and search the parent one.
   part b: If they are staggered, do we combind this into one opp up message?

* added complexity version would be to stagger the warnings in some way

Need to be addressed for both: non-mounted subvolume overlap with mounted versions of the same subvolume. Again, don't ask/warn more than we need to, and handle parent/child relationships sanely.




As many distributions use separately-mounted subvolumes by default when using btrfs, and with the increased use of lower-capacity SSDs, this behavior has high visibility.
Comment 1 André Klapper 2012-04-27 08:39:30 UTC 
Which g-s-d version is this about (please set the "Version" field)?
Comment 2 Bastien Nocera 2012-04-27 10:10:15 UTC 
If it's supposed to show up as two separate volumes, then this is the intended behaviour, and I'm not sure what exactly we'd be able to do about it.
If it's supposed to show up as a single volume, gvfs's volume monitor (and likely udisks) should do that for us.
Comment 3 Shawn Landden 2012-04-27 18:27:09 UTC 
It is two separate volumes. (sub-volumes in btrfs lingo) I just thought it was annoying that it pops up twice at the same time, for what is essentially the same low space warning. This is certainly btrfs specific, because it is the only filesystem that has this concept.
Comment 4 Shawn Landden 2012-08-04 00:57:53 UTC 
any update on if this can be fixed?
Comment 5 Tomas Bzatek 2013-04-23 13:39:14 UTC 
Can you attach `gvfs-mount -li` and `udisksctl dump` please? Let's see what's your setup exactly.
Comment 6 Bastien Nocera 2014-12-12 08:18:56 UTC 
708786 is newer, but has feedback.

*** This bug has been marked as a duplicate of bug 708786 ***