system stopped booting, cant write files, "No space left on device", even though I have ~40GB free
rebased from ublue kinoite to bazzite gnome, everything worked fine for a while, then flatpak stopped working, couldn't update because of no space left on device, even though I had around 40GB free, rebooted and I got stuck in the fedora loading screen (pictured, the loading loop icon eventually disappears and interestingly it had the fedora logo and not the new bazzite one i had seen the previous reboot) rebooted to my other boot slot that still had kinoite and i could make it into a tty, but sddm is not launching and i cant write any files (picture 2), my gf said she's seen this before and it's a panic state btrfs enters in when corrupt, is this true and is it something i can recover from without a reinstall
27 Replies
wait wat
why only one partition
more than that should be showing
df -h shows more than one, just did . to make it show /var
ah, show me all please
will do in a moment
this is from my kinoite B slot, i cant even make it to a shell on my bazzite slot
this is what it read before my last shutdown, though
i never saw something like this before... This is something SteamOS would do but not libostree systems
yeah that is very weird
and it's not like we've touched anything about iflesystems
yeah i have absolutely no clue what happened
i suppose i should just reinstall lol
you know something has gone deeply wrong when the main developer goes what the fuck
btrfsck didnt find any errors so i guess its not a filesystem corruption at least
Let's see your fstab
okay, didn't even get to running our first-boot scripts
I have no idea what this is, try deleting the bazzite deployment in ostree and rebasing again
how would i do that?
deleting the bazzite deployment
just pin your good deployment
and then run another rebase in the terminal
no space left on device strikes again
how fucking weird
yeah!
i dont know why its thinking theres no space
This is similar to what happened to me that time I broke a Kinoite install by doing nothing
I booted my PC one day and got a notification that I was out of space, it'd then freeze in SDDM or shortly after
were you able to fix it?
Nope, still no idea how it happened
dang
does it only happen on bazzite?
well considering it happened to crush running bazzite id assume not
could it be a hardware issue?
I believe that I am having this issue, too. Here is how I wrote up my description before seeing the above:
Hello, community. I'm having problems with my Bazzite desktop, and I would really appreciate some help. I have apps that fail to run, and then the OS has trouble booting. I believe the problem is that the filesystem that rpm-ostree uses is full. The ujust command to update or clean the system fails with "error: No space left on device"
Before the system became mostly unusable, I tried looking for what filesystem was out of space, but everywhere I looked I had enough free space.
About an hour before the problem occurred, I had installed Miniconda3. I uninstalled it and things got better. Then I tried installing Anaconda and the next day the problems came back. I don't understand where the disk is getting full. I could try uninstalling Anaconda, but it doesn't make sense. Can someone help me with this? Thanks in advance. Did you ever find a solution to your problem? Thanks either way. I found a solution in another thread. Clearing out tons of snapshots with btrfs-assistant resolved the issue.
About an hour before the problem occurred, I had installed Miniconda3. I uninstalled it and things got better. Then I tried installing Anaconda and the next day the problems came back. I don't understand where the disk is getting full. I could try uninstalling Anaconda, but it doesn't make sense. Can someone help me with this? Thanks in advance. Did you ever find a solution to your problem? Thanks either way. I found a solution in another thread. Clearing out tons of snapshots with btrfs-assistant resolved the issue.