Adding free space to root [Solved]

XanII · 2024-06-11 16:08:51

Checking this one out. https://forums.bunsenlabs.org/viewtopic.php?id=6849 and this https://packetpushers.net/blog/ubuntu-e … lvm-space/

Start situation: Due to reasons i had 32gb swap on latest Boron install. But i have no intentions hibernating the system so i took it down to 4gb and enabled swap back. So far so good.

So now i got 28gb of free space i would want the root partition to use. i got LVM enabled.
i do this:

root@Gordian:/home/asentaja# vgdisplay
  --- Volume group ---
  VG Name               Gordian-vg
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  4
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               <110.81 GiB
  PE Size               4.00 MiB
  Total PE              28367
  Alloc PE / Size       21199 / <82.81 GiB
  Free  PE / Size       7168 / 28.00 GiB
  VG UUID               FVasEr-dIht-iHie-MoUG-mMlQ-AzXt-Fi0ICS

'Free PE / Size' area show i got the 28GiB there free. I execute these and get note that on-line resizing required.

root@Gordian:/home/asentaja# lvextend -l +100%FREE /dev/Gordian-vg/root
  Size of logical volume Gordian-vg/root changed from 79.18 GiB (20271 extents) to 107.18 GiB (27439 extents).
  Logical volume Gordian-vg/root successfully resized.


root@Gordian:/home/asentaja# resize2fs /dev/Gordian-vg/root
resize2fs 1.47.0 (5-Feb-2023)
Filesystem at /dev/Gordian-vg/root is mounted on /; on-line resizing required
old_desc_blocks = 10, new_desc_blocks = 14
The filesystem on /dev/Gordian-vg/root is now 28097536 (4k) blocks long.

It really seems this cannot be done. I find no proper posts about it that actually works. So i guess this is something you have to do with a live CD or pivoting root to tmpfs. Or is there a easy way?

Last edited by XanII (2024-07-09 10:11:15)

johnraff · 2024-06-12 04:55:39

According to @el_koraco's tutorial it should work.

NOTE lvextend, lvreduce and lvresize (which covers both) now accept a --resizefs option, which (for many file systems - please check yours) will do the file system resizing for you at the same time, so you don't have to use those resize2fs commands or worry about getting the file system size just right.

Check your root partition size again?

Re-run lvextend with the --resizefs option?

Last edited by johnraff (2024-06-12 04:56:52)

Bearded_Blunder · 2024-06-12 07:38:35

It's my understanding that having some space in the pv (around 10%) is useful for creating snapshots for backup purposes etc. anyway.
As for the swap you generally (without hibernation) want round(sqrt(RAM)) which for 32G means a swap size of 6G. Though I'd imagine you'll get away with 4G just fine.

XanII · 2024-06-18 17:53:20

Checked filesystem. It may ok. But i may be looking at this a bit wonky but the whole disk is 120gb. Swap is down to minimum < 4gb. Where is the rest? I get it that i can't use the whole 120gb in reality as always but it seems to me more than just some gigs are wasted here.

root@Gordian:/home/asentaja# df -BG
Filesystem                   1G-blocks  Used Available Use% Mounted on
udev                               16G    0G       16G   0% /dev
tmpfs                               4G    1G        4G   1% /run
/dev/mapper/Gordian--vg-root      105G   73G       27G  74% /
tmpfs                              16G    0G       16G   0% /dev/shm
tmpfs                               1G    1G        1G   1% /run/lock
/dev/sdd2                           1G    1G        1G  29% /boot
/dev/sdb1                           1G    1G        1G  36% /boot/efi
tmpfs                               4G    1G        4G   1% /run/user/1000

Doing the lvextend with -r tells me that 107GB which was already set earlier is t here.

root@Gordian:/home/asentaja# lvextend -l +100%FREE /dev/Gordian-vg/root -r
  Size of logical volume Gordian-vg/root unchanged from 107.18 GiB (27439 extents).
  Logical volume Gordian-vg/root successfully resized.
resize2fs 1.47.0 (5-Feb-2023)
The filesystem is already 28097536 (4k) blocks long.  Nothing to do!

root@Gordian:/home/asentaja# resize2fs /dev/Gordian-vg/root
resize2fs 1.47.0 (5-Feb-2023)
The filesystem is already 28097536 (4k) blocks long.  Nothing to do!

johnraff · 2024-06-19 01:44:15

Any hint from

sudo pvdisplay -m

?

XanII · 2024-06-27 15:03:58

--- Physical volume ---
PV Name /dev/sdc3
VG Name Gordian-vg
PV Size 110.81 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 28367
Free PE 0
Allocated PE 28367
PV UUID kR0HJI-UcQD-FbSa-VNcn-VAqA-Wl33-Ygsjh0

--- Physical Segments ---
Physical extent 0 to 20270:
Logical volume /dev/Gordian-vg/root
Logical extents 0 to 20270
Physical extent 20271 to 21198:
Logical volume /dev/Gordian-vg/swap_1
Logical extents 0 to 927
Physical extent 21199 to 28366:
Logical volume /dev/Gordian-vg/root
Logical extents 20271 to 27438

Last edited by XanII (2024-06-27 15:04:31)

johnraff · 2024-06-28 02:55:56

Anyway, it looks as if your /dev/sdc3 is full.
But why are we only seeing /dev/sdc3? Are there sd1 or sd2 partitions too?

You've got two logical volumes in there mounted on /dev/Gordian-vg/root
That could be the problem.

XanII · 2024-06-29 18:34:48

asentaja@Gordian:/etc$ df -BG
Filesystem                   1G-blocks  Used Available Use% Mounted on
udev                               16G    0G       16G   0% /dev
tmpfs                               4G    1G        4G   1% /run
/dev/mapper/Gordian--vg-root      105G   77G       24G  77% /
tmpfs                              16G    0G       16G   0% /dev/shm
tmpfs                               1G    1G        1G   1% /run/lock
/dev/sdc2                           1G    1G        1G  30% /boot
/dev/sda1                           1G    1G        1G  36% /boot/efi
tmpfs                               4G    1G        4G   1% /run/user/1000
asentaja@Gordian:/etc$

And fstab for good measure

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/Gordian--vg-root /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sdb2 during installation
UUID=404b1235-b5d9-49b2-a99d-dfcc7af9c0d6 /boot           ext2    defaults        0       2
# /boot/efi was on /dev/sda1 during installation
UUID=D4E2-CCD8  /boot/efi       vfat    umask=0077      0       1
/dev/mapper/Gordian--vg-swap_1 none            swap    sw              0       0

I don't quite follow how i should have done this differently. Assign it a different name than vg-root, like vg-root_1?
been checking the docs i can find but i have not yet been able to figure out what goes wrong.

johnraff · 2024-06-30 03:07:17

I'm not an expert on this stuff (anyone?) but it looks to me as if you've got a second /dev/Gordian-vg/root Physical Segment which isn't mounted:

  Physical extent 21199 to 28366:
    Logical volume	/dev/Gordian-vg/root
    Logical extents	20271 to 27438

Could it be that the size in GB corresponding to '21199 to 28366' is the disk space you've got missing?

XanII · 2024-06-30 17:39:15

That is what i have been thinking too that i would need to mount it. But how do i mount it so it's one and the same instance and not some separate 12gb of disk.

Well i'll figure it out some day i guess.

johnraff · 2024-07-01 03:07:51

^Have you got important data on that mystery zone? If so, maybe find a way of copying it out. If not, maybe deleting it would enable you to grow the real root partition?

XanII · 2024-07-01 05:26:40

It is free space i took from the swap. Swap was 16gb and i took it down to 4gb so it's12gb of nothing.

I wonder how do i delete it in LVM when both the empty one and the one that got my system identify as /dev/Gordian-vg/root - what do i even search for in the docs.

johnraff · 2024-07-01 05:57:30

Can you back up all your system, wipe it all out and set it up again?

But before you do that, a selection of commands to try, that might tell you something...

sudo fdisk -l

blkid

lsblk

mount

ls /dev/disk/{by-id,by-label,by-path,by-uuid}

ls /dev/mapper

sudo vgdisplay

XanII · 2024-07-06 14:00:54

Wiping it all out is not feasible as this is my research case so both good and bad what i encounter here is what is the whole point of it. Also: This issue started because the installer refused to let me use any options other than the most basic 'automatic everything' setting. Even my manual attempts at sizing the disks right at the start did not work. I usually always manually build my filesystems just the way i want them but for some reason this time the installer did not work as it should have.

Now for some details....

root@Gordian:/home/asentaja# fdisk -l                                                                                          
Disk /dev/nvme0n1: 232.89 GiB, 250059350016 bytes, 488397168 sectors                                                           
Disk model: KINGSTON SA2000M8250G                                                                                              
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: dos                                                                                                            
Disk identifier: 0x469b90ac                                                                                                    

Device         Boot Start       End   Sectors   Size Id Type                                                                   
/dev/nvme0n1p1       2048 488394751 488392704 232.9G  7 HPFS/NTFS/exFAT                                                        


Disk /dev/sdc: 111.79 GiB, 120034123776 bytes, 234441648 sectors                                                               
Disk model: KINGSTON SV300S3                                                                                                   
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: A3EC65A2-3144-4942-8CC6-72104388A03C                                                                          

Device       Start       End   Sectors   Size Type                                                                             
/dev/sdc1     2048   1050623   1048576   512M EFI System                                                                       
/dev/sdc2  1050624   2050047    999424   488M Linux filesystem                                                                 
/dev/sdc3  2050048 234440703 232390656 110.8G Linux LVM                                                                        


Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors                                                               
Disk model: KINGSTON SUV5004                                                                                                   
Units: sectors of 1 * 512 = 512 bytes                                                                                          
Sector size (logical/physical): 512 bytes / 4096 bytes                                                                         
I/O size (minimum/optimal): 4096 bytes / 4096 bytes                                                                            
Disklabel type: gpt                                                                                                            
Disk identifier: 97BEB183-36BD-4C40-9062-8B5B7350ED62                                                                          

Device     Start       End   Sectors   Size Type                                                                               
/dev/sdb1     34     32767     32734    16M Microsoft reserved                                                                 
/dev/sdb2  32768 937699327 937666560 447.1G Microsoft basic data                                                               

Partition 1 does not start on physical sector boundary.
Disk /dev/sdd: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: CT500MX500SSD1  
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: dos
Disk identifier: 0x32a2d391

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdd1        2048 976769023 976766976 465.8G  7 HPFS/NTFS/exFAT


Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 870 
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: 2B19882F-5F16-4640-B0CF-FD7A20C8A26C

Device         Start       End   Sectors  Size Type
/dev/sda1       2048    206847    204800  100M EFI System
/dev/sda2     206848    239615     32768   16M Microsoft reserved
/dev/sda3     239616 486807551 486567936  232G Microsoft basic data
/dev/sda4  486807552 488394751   1587200  775M Windows recovery environment


Disk /dev/mapper/Gordian--vg-root: 107.18 GiB, 115087507456 bytes, 224780288 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/mapper/Gordian--vg-swap_1: 3.63 GiB, 3892314112 bytes, 7602176 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
root@Gordian:/home/asentaja#

blkid command....

root@Gordian:/home/asentaja# blkid
/dev/mapper/Gordian--vg-swap_1: UUID="5cc54963-ac34-4b97-8f90-0882a31a7cf9" TYPE="swap"
/dev/nvme0n1p1: LABEL="Maximus" BLOCK_SIZE="512" UUID="38709D65709D2AA0" TYPE="ntfs" PARTUUID="469b90ac-01"
/dev/sdd1: LABEL="Varus" BLOCK_SIZE="512" UUID="325033045032CE7B" TYPE="ntfs" PARTUUID="32a2d391-01"
/dev/sdb2: LABEL="Sirius" BLOCK_SIZE="512" UUID="981C578D1C576572" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d5871471-a25b-452a-a65d-ff524c6e520e"
/dev/mapper/Gordian--vg-root: UUID="64e0a563-828b-4192-b8fe-8a2ded4a46c8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc2: UUID="404b1235-b5d9-49b2-a99d-dfcc7af9c0d6" BLOCK_SIZE="1024" TYPE="ext2" PARTUUID="7f6bcc99-e428-4c29-ac91-bfde0caf69f8"
/dev/sdc3: UUID="kR0HJI-UcQD-FbSa-VNcn-VAqA-Wl33-Ygsjh0" TYPE="LVM2_member" PARTUUID="589cd5cf-2faf-4d45-a898-54118407a125"
/dev/sdc1: UUID="7443-F6F1" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="739303ee-e564-4c92-ad05-e9948d1339e5"
/dev/sda4: BLOCK_SIZE="512" UUID="0452934052933600" TYPE="ntfs" PARTUUID="13bcc2c5-1255-40b2-a05d-245653a8c368"
/dev/sda3: LABEL="Curia" BLOCK_SIZE="512" UUID="80B6E43DB6E434F6" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9ad73b86-7ae0-4ca6-badc-5c8463a894f3"
/dev/sda1: UUID="D4E2-CCD8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="72e5387d-101e-41fd-8119-8e0e1dcfda69"
/dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="21d24379-7363-4792-b147-5e34476cd1bc"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="5279473d-3efd-4d65-91ec-6304ae252d3c"
root@Gordian:/home/asentaja#

lsblk command:

root@Gordian:/home/asentaja# lsblk
NAME                   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                      8:0    0 232.9G  0 disk 
├─sda1                   8:1    0   100M  0 part /boot/efi
├─sda2                   8:2    0    16M  0 part 
├─sda3                   8:3    0   232G  0 part 
└─sda4                   8:4    0   775M  0 part 
sdb                      8:16   0 447.1G  0 disk 
├─sdb1                   8:17   0    16M  0 part 
└─sdb2                   8:18   0 447.1G  0 part 
sdc                      8:32   0 111.8G  0 disk 
├─sdc1                   8:33   0   512M  0 part 
├─sdc2                   8:34   0   488M  0 part /boot
└─sdc3                   8:35   0 110.8G  0 part 
  ├─Gordian--vg-root   254:0    0 107.2G  0 lvm  /
  └─Gordian--vg-swap_1 254:1    0   3.6G  0 lvm  [SWAP]
sdd                      8:48   0 465.8G  0 disk 
└─sdd1                   8:49   0 465.8G  0 part 
nvme0n1                259:0    0 232.9G  0 disk 
└─nvme0n1p1            259:1    0 232.9G  0 part 
root@Gordian:/home/asentaja#

mount command

root@Gordian:/home/asentaja# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=16206184k,nr_inodes=4051546,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3247020k,mode=755,inode64)
/dev/mapper/Gordian--vg-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=27863)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
/dev/sdc2 on /boot type ext2 (rw,relatime)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3247016k,nr_inodes=811754,mode=700,uid=1000,gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
root@Gordian:/home/asentaja#

disk by-x outputs

root@Gordian:/home/asentaja# ls /dev/disk/by-id
ata-CT500MX500SSD1_2244E67FEC75
ata-CT500MX500SSD1_2244E67FEC75-part1
ata-KINGSTON_SUV500480G_50026B7782451A69
ata-KINGSTON_SUV500480G_50026B7782451A69-part1
ata-KINGSTON_SUV500480G_50026B7782451A69-part2
ata-KINGSTON_SV300S37A120G_50026B775A00944F
ata-KINGSTON_SV300S37A120G_50026B775A00944F-part1
ata-KINGSTON_SV300S37A120G_50026B775A00944F-part2
ata-KINGSTON_SV300S37A120G_50026B775A00944F-part3
ata-Samsung_SSD_870_EVO_250GB_S6PENL0X208481J
ata-Samsung_SSD_870_EVO_250GB_S6PENL0X208481J-part1
ata-Samsung_SSD_870_EVO_250GB_S6PENL0X208481J-part2
ata-Samsung_SSD_870_EVO_250GB_S6PENL0X208481J-part3
ata-Samsung_SSD_870_EVO_250GB_S6PENL0X208481J-part4
dm-name-Gordian--vg-root
dm-name-Gordian--vg-swap_1
dm-uuid-LVM-FVasErdIhtiHieMoUGmMlQAzXtFi0ICSgoe88teb7K89vKAd7Dc9Lg4ht41uWnPd
dm-uuid-LVM-FVasErdIhtiHieMoUGmMlQAzXtFi0ICSQXGUYl2W4i9wTggZgooKcaPqfi7dOG8L
lvm-pv-uuid-kR0HJI-UcQD-FbSa-VNcn-VAqA-Wl33-Ygsjh0
nvme-eui.0026b728241ecd65
nvme-eui.0026b728241ecd65-part1
nvme-KINGSTON_SA2000M8250G_50026B728241ECD6
nvme-KINGSTON_SA2000M8250G_50026B728241ECD6_1
nvme-KINGSTON_SA2000M8250G_50026B728241ECD6_1-part1
nvme-KINGSTON_SA2000M8250G_50026B728241ECD6-part1
wwn-0x5002538f54239a29
wwn-0x5002538f54239a29-part1
wwn-0x5002538f54239a29-part2
wwn-0x5002538f54239a29-part3
wwn-0x5002538f54239a29-part4
wwn-0x50026b775a00944f
wwn-0x50026b775a00944f-part1
wwn-0x50026b775a00944f-part2
wwn-0x50026b775a00944f-part3
wwn-0x50026b7782451a69
wwn-0x50026b7782451a69-part1
wwn-0x50026b7782451a69-part2
wwn-0x500a0751e67fec75
wwn-0x500a0751e67fec75-part1
root@Gordian:/home/asentaja# 


root@Gordian:/home/asentaja# ls /dev/disk/by-label/
Curia  Maximus  Sirius  Varus
root@Gordian:/home/asentaja# 


root@Gordian:/home/asentaja# ls /dev/disk/by-path/
pci-0000:02:00.0-nvme-1         pci-0000:0f:00.0-ata-1-part1    pci-0000:0f:00.0-ata-2-part1    pci-0000:0f:00.0-ata-3-part2
pci-0000:02:00.0-nvme-1-part1   pci-0000:0f:00.0-ata-1-part2    pci-0000:0f:00.0-ata-2-part2    pci-0000:0f:00.0-ata-3-part3
pci-0000:0f:00.0-ata-1          pci-0000:0f:00.0-ata-1-part3    pci-0000:0f:00.0-ata-3          pci-0000:0f:00.0-ata-4
pci-0000:0f:00.0-ata-1.0        pci-0000:0f:00.0-ata-1-part4    pci-0000:0f:00.0-ata-3.0        pci-0000:0f:00.0-ata-4.0
pci-0000:0f:00.0-ata-1.0-part1  pci-0000:0f:00.0-ata-2          pci-0000:0f:00.0-ata-3.0-part1  pci-0000:0f:00.0-ata-4.0-part1
pci-0000:0f:00.0-ata-1.0-part2  pci-0000:0f:00.0-ata-2.0        pci-0000:0f:00.0-ata-3.0-part2  pci-0000:0f:00.0-ata-4-part1
pci-0000:0f:00.0-ata-1.0-part3  pci-0000:0f:00.0-ata-2.0-part1  pci-0000:0f:00.0-ata-3.0-part3
pci-0000:0f:00.0-ata-1.0-part4  pci-0000:0f:00.0-ata-2.0-part2  pci-0000:0f:00.0-ata-3-part1
root@Gordian:/home/asentaja# 

root@Gordian:/home/asentaja# ls /dev/disk/by-uuid/
0452934052933600  404b1235-b5d9-49b2-a99d-dfcc7af9c0d6  7443-F6F1         D4E2-CCD8
325033045032CE7B  5cc54963-ac34-4b97-8f90-0882a31a7cf9  80B6E43DB6E434F6
38709D65709D2AA0  64e0a563-828b-4192-b8fe-8a2ded4a46c8  981C578D1C576572
root@Gordian:/home/asentaja#

ls /dev/mapper

root@Gordian:/home/asentaja# ls /dev/mapper
control  Gordian--vg-root  Gordian--vg-swap_1
root@Gordian:/home/asentaja#

sudo vgdisplay

root@Gordian:/home/asentaja# vgdisplay
  --- Volume group ---
  VG Name               Gordian-vg
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               <110.81 GiB
  PE Size               4.00 MiB
  Total PE              28367
  Alloc PE / Size       28367 / <110.81 GiB
  Free  PE / Size       0 / 0   
  VG UUID               FVasEr-dIht-iHie-MoUG-mMlQ-AzXt-Fi0ICS
   
root@Gordian:/home/asentaja#

Note on the above disks: Only the disk that has slightly below 120gb is used by Bunsen. The other disks are the windows partitions i used before firing up bunsen. They are not used on the linux side in any way or form.

Last edited by XanII (2024-07-06 14:02:24)

johnraff · 2024-07-08 07:05:41

XanII wrote:

Wiping it all out is not feasible as this is my research case so both good and bad what i encounter here is what is the whole point of it.

My suggestion was to backup your data, then wipe out and start again. Are you saying that that's not feasable because this is a learning exercise for you? In that case, there's surely a limit to how much help you can reasonably ask from others?

This issue started because the installer refused to let me use any options other than the most basic 'automatic everything' setting. Even my manual attempts at sizing the disks right at the start did not work. I usually always manually build my filesystems just the way i want them but for some reason this time the installer did not work as it should have.

Are you referring to the installer on a recent BL iso, like Boron? I've never had any such issues with that installer, which is just the Debian Installer anyway, with some configurations preset.

Now for some details....

Thanks.
Do you see any hints in there as to what is happening?

Note on the above disks: Only the disk that has slightly below 120gb is used by Bunsen. The other disks are the windows partitions i used before firing up bunsen. They are not used on the linux side in any way or form.

So the disk you are concerned about is /dev/sdc right?

Now, I see a difference in the output of vgdisplay, compared with your first post:

XanII's first post wrote:

root@Gordian:/home/asentaja# vgdisplay
  --- Volume group ---
  VG Name               Gordian-vg
  Alloc PE / Size       21199 / <82.81 GiB
  Free  PE / Size       7168 / 28.00 GiB

Compared with now:

root@Gordian:/home/asentaja# vgdisplay
  --- Volume group ---
  VG Name               Gordian-vg
  Alloc PE / Size       28367 / <110.81 GiB
  Free  PE / Size       0 / 0

That looks rather as if the whole 110GiB of Gordian-vg is now allocated, where before it was only ~82Gib - a gain of 28GiB.

Isn't your issue solved?

One more command I forgot to suggest:

sudo lvdisplay Gordian-vg

XanII · 2024-07-08 07:20:23

Yes it does look like the issue is indeed taken care of. I did say earlier i was looking at this a bit wonky e.g. i can't quite read the output.

But it is a good learning opportunity. And yes you are right about there being a limit to how much help can be asked. It is a finite resource indeed and i don't want to bother people too much.

johnraff · 2024-07-08 09:25:57

^But don't let that stop you from asking questions!

#1 2024-06-11 16:08:51

Adding free space to root [Solved]

#2 2024-06-12 04:55:39

Re: Adding free space to root [Solved]

#3 2024-06-12 07:38:35

Re: Adding free space to root [Solved]

#4 2024-06-18 17:53:20

Re: Adding free space to root [Solved]

#5 2024-06-19 01:44:15

Re: Adding free space to root [Solved]

#6 2024-06-27 15:03:58

Re: Adding free space to root [Solved]

#7 2024-06-28 02:55:56

Re: Adding free space to root [Solved]

#8 2024-06-29 18:34:48

Re: Adding free space to root [Solved]

#9 2024-06-30 03:07:17

Re: Adding free space to root [Solved]

#10 2024-06-30 17:39:15

Re: Adding free space to root [Solved]

#11 2024-07-01 03:07:51

Re: Adding free space to root [Solved]

#12 2024-07-01 05:26:40

Re: Adding free space to root [Solved]

#13 2024-07-01 05:57:30

Re: Adding free space to root [Solved]

#14 2024-07-06 14:00:54

Re: Adding free space to root [Solved]

#15 2024-07-08 07:05:41

Re: Adding free space to root [Solved]

#16 2024-07-08 07:20:23

Re: Adding free space to root [Solved]

#17 2024-07-08 09:25:57

Re: Adding free space to root [Solved]

Board footer