On Sunday, 11 May 2025 13:21:34 British Summer Time Dale wrote: > Michael wrote: > > On Sunday, 11 May 2025 06:41:46 British Summer Time Dale wrote: > >> Howdy, > >> > >> I'm updating my old rig. Well, I'm trying to. I kept running out of > >> space while compiling rust. I need to make /var larger. > > > > There are some alternatives to this, especially for rust: > > > > 1. First of all not compile it locally. You could use rust-bin, or you > > could use the gentoo binhost package if your USE flags are default, or > > compile it on another PC of yours which has enough space, using > > appropriate C, CPU and USE flags and then bring it over to this PC to > > emerge it as a binary. [snip ...]
> Well, I still like to compile my own, that way I can use my own USE > flags and such. [snip ...] > >> root@fireball / # pvs > >> > >> PV VG Fmt Attr PSize PFree > >> /dev/sda7 OS lvm2 a-- <124.46g 5.39g > >> > >> root@fireball / # vgs > >> > >> VG #PV #LV #SN Attr VSize VFree > >> OS 1 3 0 wz--n- <124.46g 5.39g > >> > >> root@fireball / # lvs > >> > >> LV VG Attr LSize Pool Origin Data% Meta% Move Log > >> > >> Cpy%Sync Convert > >> > >> swap OS -wi-ao---- > >> > >> 12.00g > >> > >> usr OS -wi-ao---- > >> > >> 39.06g > >> > >> var OS -wi-ao---- > >> > >> 68.00g > >> > >> root@fireball / # resize2fs /dev/mapper/OS-var > >> resize2fs 1.47.2 (1-Jan-2025) > >> open: Device or resource busy while opening /dev/mapper/OS-var > >> root@fireball / # > > > > Err ... what is this 'OS-var'? > > I named it OS-var when I set up LVM. That way I know it is OS related > and is the /var directory. I named /usr OS-usr too. :-D Try: lvdisplay vgdisplay pvdisplay Your lvs output shows VG named "OS" and the LV named as "var". As I understand this, subdirectories of /dev/mapper/ would be VGs. The /dev/ VG/LV nomenclature should be used to perform a resize on the LV. Try 'lvscan' to see what path to use for the resize command.
signature.asc
Description: This is a digitally signed message part.
