Open Bug 2054238 Opened 1 month ago Updated 16 hours ago

It keeps alerting me that i don't have space in disk but I have

Categories

(Core :: Storage: Quota Manager, defect)

Product:
Core
Component:
Storage: Quota Manager
Version:
Firefox 152
Platform:
x86_64
Linux
Type:
defect

Tracking

()

People

(Reporter: lucasalves.ppl, Unassigned)

Details

Attachments

(1 file)

proves.png
116.56 KB, image/png
Details
Attached image proves.png —

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0

Steps to reproduce:

I've just formatted my PC (use to have Windows 11 and changed to CachyOS), opened firefox, logged in my mozilla account to keep my passwords and favorites, installed a extension (don't remember the name of it since i removed it right after, but it was kinda famous) for it to run through all my favorites and the icons show up again.

(i'm brazilian so sorry for the prints in portuguese)

Actual results:

now it keeps showing up this "no space in disk available" since i have space in disk available

i'm brazilian so sorry for the prints in portuguese, but these are:

  • the alert "Firefox is running out of disk space. Some website content may not be displayed correctly. You can manage stored website data in Preferences > Privacy & Security > Cookies and Site Data."
  • status of my system showing that i've used 23% of it and it has 400gb available
  • *Manage Cookies and Site Data showing 1,1gb of usage

Expected results:

? not showing the alert

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Not sure which component the widget is.

Component: Widget: Gtk → General
Product: Core → Firefox

Please go to about:support and paste your 'profile folder' and binary folder. We want to make sure your profile folder is not in a partition that has no space

(In reply to rrando from comment #3)

Please go to about:support and paste your 'profile folder' and binary folder. We want to make sure your profile folder is not in a partition that has no space

Application Binary:
/usr/lib/firefox/firefox

Profile Folder:
/home/user/.config/mozilla/firefox/6xioqrk8.default-release

(In reply to Martin Stránský [:stransky] (ni? me) from comment #2)

Not sure which component the widget is.

by "widget" I mean the warning banner shown at the top of the Firefox window that says "Firefox is running out of disk space.". I'm not sure which bugzilla component it belongs to either

Severity: -- → S2
Status: UNCONFIRMED → NEW
Component: General → Storage: Quota Manager
Ever confirmed: true
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64

Thanks for the report. That "running out of disk space" warning comes from Firefox's storage quota system, which checks free space on the specific filesystem/partition where your profile lives — not your whole disk. So it's possible for the system to show 400GB free overall while the partition holding ~/.config/mozilla/firefox/ is constrained (or is being reported oddly). This is especially common right after a migration to a new OS/filesystem.

To help us pin this down, could you provide:

  1. Filesystem layout — output of:
    df -h
    df -h ~/.config/mozilla/firefox/
    findmnt -no SOURCE,FSTYPE,SIZE,AVAIL,USED --target ~/.config/mozilla/firefox/
  2. This tells us the partition, filesystem type, and actual free space where your profile resides.
  3. Filesystem type — CachyOS often defaults to btrfs. If you're on btrfs, please also run:
    btrfs filesystem usage /home
  4. (btrfs can report free space in ways that differ from a simple check, and snapshots can consume space that isn't obvious.)
  5. Fresh profile test — create a new profile via about:profiles located on a partition you know has plenty of room, browse for a bit, and let us know whether the warning still appears.
  6. The full text of the warning and, if possible, a screenshot.

Filesystem layout

df -h:

Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p2  473G   64G  409G  14% /
devtmpfs        3.8G     0  3.8G   0% /dev
tmpfs           3.9G   42M  3.8G   2% /dev/shm
efivarfs        128K  9.1K  114K   8% /sys/firmware/efi/efivars
tmpfs           1.6G  1.8M  1.6G   1% /run
none            1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
none            1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
/dev/nvme0n1p2  473G   64G  409G  14% /root
/dev/nvme0n1p2  473G   64G  409G  14% /home
tmpfs           3.9G  8.9M  3.9G   1% /tmp
/dev/nvme0n1p2  473G   64G  409G  14% /srv
/dev/nvme0n1p2  473G   64G  409G  14% /var/log
/dev/nvme0n1p2  473G   64G  409G  14% /var/cache
/dev/nvme0n1p1  4.0G  794M  3.3G  20% /boot
/dev/nvme0n1p2  473G   64G  409G  14% /var/tmp
tmpfs           786M   61M  725M   8% /run/user/1000
fuse-overlayfs  786M   61M  725M   8% /run/user/1000/psd/lucassorrizo-firefox-tcq2m7to.default
fuse-overlayfs  786M   61M  725M   8% /run/user/1000/psd/lucassorrizo-firefox-6xioqrk8.default-release
fuse-overlayfs  786M   61M  725M   8% /run/user/1000/psd/lucassorrizo-google-chrome

df -h ~/.config/mozilla/firefox/:

Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p2  473G   64G  409G  14% /home

findmnt -no SOURCE,FSTYPE,SIZE,AVAIL,USED --target ~/.config/mozilla/firefox/:

/dev/nvme0n1p2[/@home] btrfs 472.9G 408.4G 63.6G

btrfs filesystem usage /home:

Overall:
    Device size:          472.94GiB
    Device allocated:      76.02GiB
    Device unallocated:   396.91GiB
    Device missing:          0.00B
    Device slack:            0.00B
    Used:                  63.48GiB
    Free (estimated):     408.37GiB (min: 209.91GiB)
    Free (statfs, df):    408.37GiB
    Data ratio:              1.00
    Metadata ratio:          2.00
    Global reserve:      150.33MiB (used: 0.00B)
    Multiple profiles:         no

Data,single: Size:72.01GiB, Used:60.55GiB (84.09%)
Metadata,DUP: Size:2.00GiB, Used:1.46GiB (73.19%)
System,DUP: Size:8.00MiB, Used:16.00KiB (0.20%)

I will also create a fresh Firefox profile and report

Arnaud, this might be of interest to you

Flags: needinfo?(abienner)

Thanks Sam.

We discussed about this bug during our team meeting and I'll try to summarize our discussion:
It's possible (likely) that the error is coming from website/domain which has been using all its quota.
Apparently (I didn't check myself) we don't make a distinction between "disk full" and "quota full" (same error code), and this is definitely something we should improve, if confirmed.
We probably have duplicate of this bug around (will need to check for those).

Jari: could you please confirm I summarized this correctly?

Flags: needinfo?(abienner) → needinfo?(jjalkanen)

Lucas: could you please let us know if this happens on any website, or some in particular?

Flags: needinfo?(lucasalves.ppl)

(In reply to Arnaud Bienner from comment #10)

Lucas: could you please let us know if this happens on any website, or some in particular?

I first noticed the issue while using web.whatsapp.com. Whenever the "Firefox is running out of disk space" notification appeared, WhatsApp would disconnect my account.

Since then, whenever this happens, I usually do the following:

  • Clear the temporary cached files and pages (for all websites), which is usually around 1 GB.
  • Then go to "Manage Data" under the site data settings and specifically remove the data for WhatsApp, which is usually around 1.4 GB.
  • Log back into my WhatsApp account.

After doing this, WhatsApp works normally again until the notification appears again.

Flags: needinfo?(lucasalves.ppl)

It's possible (likely) that the error is coming from website/domain which has been using all its quota.
Apparently (I didn't check myself) we don't make a distinction between "disk full" and "quota full" (same error code), and this is definitely something we should improve, if confirmed.
We probably have duplicate of this bug around (will need to check for those).

Jari: could you please confirm I summarized this correctly?

The summary is correct. Based on the report, it seems like either more than usual is getting stored to localstorage which has a low quota limit, only about 5MB (maybe it's used as a fallback?), or the site triggers a defect which throws the quota values off. Because we don't want to encourage sites to try to find out how much free disk space a user has, we consider the quota allocation as a "virtual disk" and don't make a site-visible distinction between the two. What's important is that the site can't use more space before cleaning up.

Flags: needinfo?(jjalkanen)

I think I've found the root cause of your problem/quota exceed error: it's because your profile is stored on a relatively small partition (psd/profile-sync-daemon is doing that):

fuse-overlayfs  786M   61M  725M   8% /run/user/1000/psd/lucassorrizo-firefox-6xioqrk8.default-release

Firefox's rule for quota is:

  1. tempStorageLimit = 50% of disk capacity, capped at 8 TB [1]
  2. Then the group limit (per eTLD+1) is: min(tempStorageLimit / 5, 10 GB), with a floor of 10 MB [2]

So in your case, with 786M, we have:

  1. Temp storage limit = 50% of 786 MB = ~393 MB
  2. Group limit = min(393 MB / 5, 10 GB) = ~78 MB

And 78MB is relatively small: it's likely to be quickly filled, and data eviction to fail, triggering this "no disk space left" banner you saw.

It's psd (profile-sync-daemon) which is creating those small partitions and loading your profile in.
I couldn't find a duplicate within bugzilla, but found someone reported this issue on CachyOS forum:
https://discuss.cachyos.org/t/run-user-1000-is-almost-full-and-firefox-is-running-out-of-disk-space/23135

Apparently it does that to try to make Firefox faster, because the full profile will remain in RAM fs, so it read/write are faster (because they don't go through the disk).
I'm not sure to which point this is the correct thing to do, and how much benefit this brings because all modern operating systems (including Linux) cache data from disk in RAM anyway, making only the first accesses slower.
And this could lead to data corruption: we have mechanism in Firefox to flush data to disk at certain point in time: with this mechanism, we are actually flushing to RAM (FS) so if your system crashes (power cut, kernel panic, ...) I'm afraid the data might not have been saved to disk, even though I expect psd to regularly sync the partition with the disk, but we have no control over that.

I would suggest you to check with the CachyOS community to get their opinion about that, and meanwhile, to disable psd for Firefox on your system: this will just make Firefox work like on any Linux system, so it should be a safe thing to do.

Now a second issue is that warning banner: I think the "Firefox is running out of disk space" message is misleading.
Even with a small partition (786 MB here) you will hit this message when trying to store more than 78MB, so your disk isn't full: it's simply quota that has reached its limit.

IMHO we should change it to something less confusing...

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: