Need to resize btrfs partition. commands not working as expected. Do I have to reinstall?

English Install/Boot/Login
#1

So I installed Tumbleweed. I used it for a week, loved it. Took a few days break during a move, then forgot my root PW. I only had this laptop at the time and no suse image. So I installed windows from a usb, made bootable openSUSE installer and

I installed Tumbleweed again. This time I made sure to make a root PW I liked. I re-setup my environment and everything just how I like it. Did tons of configuration. I was just ironing out some docker containers when I realized:
The btrfs partition containing /usr /home /var etc. is nearing is 35GB capacity. Because I didn’t properly remove the 400GB windows partition. I used the Yaml tool to delete the 400GB windows partition, but there doesn’t seem to be a way to increase the current one (mounted). The system is running on a single 500gb internal nvme. I tried the yast tool and the btrs commands with no luck.

Is there a way to increase the partition/filesystem so I can continue using opensuse? Otherwise is there a way to reinstall and recovery the majority of my packages and configuration?

Also I do get an error occasionally since the first boot on my current installation, so is there a way to inspect the tumbleweed filesystem and fix missing/corrupt files?

Thanks

#2

filesystem
filesystem1001Ă—500 37.4 KB

#3

Show output of fdisk -l. And please, do not post pictures to show text information. Is it that difficult to copy and paste from terminal? Post computer output as preformatted text (</> button in editor).

#4

sorry for previous formatting

isk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO 500GB               
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 841A4ABB-F092-4DCF-B5E1-648E0E288D97

Device             Start       End  Sectors  Size Type
/dev/nvme0n1p1      2048    206847   204800  100M EFI System
/dev/nvme0n1p2    206848    239615    32768   16M Microsoft reserved
/dev/nvme0n1p4 975728640 976771071  1042432  509M Windows recovery environment
/dev/nvme0n1p5 898131968 971534335 73402368   35G Linux filesystem
/dev/nvme0n1p6 971534336 975728639  4194304    2G Linux swap

Partition table entries are not in disk order.


Disk /dev/loop0: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 349.69 MiB, 366678016 bytes, 716168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 79.6 MiB, 83468288 bytes, 163024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 249.89 MiB, 262029312 bytes, 511776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 164.82 MiB, 172830720 bytes, 337560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 63.45 MiB, 66527232 bytes, 129936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 55.66 MiB, 58368000 bytes, 114000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop8: 53.26 MiB, 55844864 bytes, 109072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
#5

I am not quite sure what you want. But when it is that you want to increase the size of the Btrfs file system that is on /dev/nvme0n1p5, then you are out of luck. There is no adjacent space (most file system types can only increase at their end when at all, but I am not sure if Btrfs can also increase at the front).

#6

Did you delete the windows partition? Because fdisk shows this for me

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     206847     204800   100M EFI System
/dev/nvme0n1p2     206848     239615      32768    16M Microsoft reserved
/dev/nvme0n1p3     239616  732596223  732356608 349.2G Microsoft basic data
/dev/nvme0n1p4  732596224  734001151    1404928   686M Windows recovery environm
/dev/nvme0n1p5  734001152 1949329407 1215328256 579.5G Linux filesystem
/dev/nvme0n1p6 1949329408 1953525134    4195727     2G Linux swap

You’re missing the “Microsoft basic data”.

If you don’t want Windows anymore, you could TRY (you could lose data so backup first) to spin up a bootable USB with GParted and:

  • Delete the “Microsoft reserved partition”
  • Delete the “Windows recovery environment”
  • Move the “Linux filesystem” to the left - It’s gonna take a lot of time
  • Extend the “Linux filesystem” partition to the right
  • Extend the btrfs filesystem

You could also just create a new btrfs partition in the empty space and then add a new device to your btrfs filesystem.

1 Like