xtapa

@ xtapa @discuss.tchncs.de

Posts

21
Comments

128
Joined

2 yr. ago

4d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space
Jump
xtapa @discuss.tchncs.de 4d ago
Fair enough :)

5d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space

btrfs scrub it is, but it did not do much, but i followed some clean up tipps and could free 34gb of stuff, so for now I'm good I guess :D

5d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space

Jump

xtapa @discuss.tchncs.de 5d ago

I chose the disk because before the switch everyone was boasting about how Linux doesn't need much space 😅

I see what I can do, I deleted almost all snapshots and they get cleared after each system update so I have only a hand full.

5d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space

Jump

xtapa @discuss.tchncs.de 5d ago

UEFI Boot menu. Meanwhile, I managed to run GRUB, boot from another snapshot, set a new default and delete the culprit #835. Freed up some space, but still my disk is full, so now I need to find out why I guess.

5d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space

Jump

xtapa @discuss.tchncs.de 5d ago

I managed to get into grub after editing the config in yast. I booted into a current snapshot and deleted most old ones, including the old 835.

Still, my disc usage is at 118 / 120gb. I cleaned up all zypper stuff that is orphaned and unneeded.

My snapper list output is now

0 │ single │ root │ current 1828 │ pre │ Fr 16 Jan 2026 17:05:39 CET │ root │ 1.76 GiB │ number │ yast snapper 1832* │ single │ Fr 16 Jan 2026 17:17:41 CET │ root │ 272.00 KiB │ writable copy of #1807

And some snapshot from all the cleanup. Looks like the #835 entry before and I kinda get the feeling ChatGPT led to wrong conclusions.

So now I need to find out why my disk space is still fucked :( Starting with btrfs cleanup I guess. Do you have any suggestions?

5d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space

Jump

xtapa @discuss.tchncs.de 5d ago

If your home partition part of the same filesystem then filling your home with games and media also shows as filling root also, because its all one volume.

I have ~/Misc and ~/Games mounted to two different drives and when I last checked (has been a while tbh) these drives would not affect the display for root. I remember having an eye on it in the beginning because I wasn't sure I hooked up the drives correctly.

If you don’t like CLI stuff then: You can review grub menu options in the YAST2 GUI app for boot. Here you will see if there is a delay set to pick an alternate snapshot, or boot direct.

I tried updating GRUB delay via the config file but could not apply the changes. I didn't even think about YAST. What a good call! I'll try this.

But first use YAST2 GUI to review Filesystem, it will show you how many snap shots you have and whether they are important or not. You can also set how long to keep them by time or by number of entries. You can delete old ones if you don’t need them. You can force a new snapshot. But I would clear disk space first if you are that full.

I forgot to add my snapper list output in the inital post and added it later. I have only 8 snapshots as older snapshots get deleted automatically. There is "#0 current", "#835" from back in 2024 and 6 recent snapshots. Each a snap before an update and after an update. From what I understand, my system keeps booting in the old #835 snapshot (I guess I did something wrong during a rollback) that now keeps growing after every system update.

How have your " sudo zypper dup" upgrades gone?

For the last 2 years they went through without noticable issues.

5d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space

Jump

xtapa @discuss.tchncs.de 5d ago

When you are using the livecd are you booting all the way to the Ubuntu desktop?

Yes, I selected the "Install / Try" entry.

What gives you the nvme device name error?

I ran "sudo btrfs subvolume list /dev/nvme1n1p2" and got the errors:

    
ERROR: not a directory: /dev/nvme1n1p2 
ERROR: can't access '/dev/nvme1n1p2'

I think ChatGPT interpreted or assumed that theres a difference between how they are named in Ubuntu vs. how they are named in my actual system.

The output (run from my system, not from the Ubuntu Live System) of "df -h" is:

... /dev/nvme1n1p2 119G 113G 3.1G 98% / /dev/nvme1n1p1 511M 6.3M 505M 2% /boot/efi ...

5d ago

[OpenSUSE Tumbleweed] Stuck in a writable snapshot that eats up all my system disc space

Jump

xtapa @discuss.tchncs.de 5d ago

The amount of snapshots isn't the problem. Sry, I forgot to add my snapper list output, but added it now. I only have 8 snapshots, when a new snapshot is made, the oldest is deleted (except for the unused current and the wrongly used #835).

It's the #835 snapshot that seems to be taking up all the space.