El mar, 5 jul 2022 a las 8:39, Miroslav Skoric (<sko...@uns.ac.rs>) escribió: > > On 7/5/22 9:37 AM, Tom Dial wrote: > > > > Post the output from > > > > # fdisk -l (or $ sudo fdisk -l) > > # vgdisplay -v (or $ sudo vgdisplay -v) > > > > Here it is: > > # fdisk -l > Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors > Disk model: Hitachi HTS54323 > 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: 0x0005de22 > > Device Boot Start End Sectors Size Id Type > /dev/sda1 * 2048 499711 497664 243M 83 Linux > /dev/sda2 501758 625141759 624640002 297.9G 5 Extended > /dev/sda5 501760 625141759 624640000 297.9G 83 Linux > > > > > Disk /dev/mapper/sda5_crypt: 297.9 GiB, 319814627328 bytes, 624637944 > 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/localhost-root: 5.3 GiB, 5716836352 bytes, 11165696 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/localhost-usr: 13.4 GiB, 14365491200 bytes, 28057600 > 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/localhost-var: 2.8 GiB, 2998927360 bytes, 5857280 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/localhost-swap_1: 5.7 GiB, 6090129408 bytes, 11894784 > 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/localhost-tmp: 2.4 GiB, 2545942528 bytes, 4972544 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/localhost-home: 261 GiB, 280246616064 bytes, 547356672 > 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 > > > > > # vgdisplay -v > --- Volume group --- > VG Name localhost > System ID > Format lvm2 > Metadata Areas 1 > Metadata Sequence No 17 > VG Access read/write > VG Status resizable > MAX LV 0 > Cur LV 6 > Open LV 6 > Max PV 0 > Cur PV 1 > Act PV 1 > VG Size <297.85 GiB > PE Size 4.00 MiB > Total PE 76249 > Alloc PE / Size 74378 / <290.54 GiB > Free PE / Size 1871 / <7.31 GiB > VG UUID fbCaw1-u3SN-2HCy-w6y8-v0nK-QsFE-FETNZM > > --- Logical volume --- > LV Path /dev/localhost/root > LV Name root > VG Name localhost > LV UUID z3MLJc-UsXY-hxOE-xSk2-ipAl-NUny-PDpXv6 > LV Write Access read/write > LV Creation host, time , > LV Status available > # open 1 > LV Size 5.32 GiB > Current LE 1363 > Segments 2 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:1 > > --- Logical volume --- > LV Path /dev/localhost/usr > LV Name usr > VG Name localhost > LV UUID UbFZNN-Y0oA-tEAb-5a8g-z65r-Ekqv-agbmrc > LV Write Access read/write > LV Creation host, time , > LV Status available > # open 1 > LV Size <13.38 GiB > Current LE 3425 > Segments 2 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:2 > > --- Logical volume --- > LV Path /dev/localhost/var > LV Name var > VG Name localhost > LV UUID yljPiS-bfh3-w0vA-fAg9-anAE-OaiF-XgvyoY > LV Write Access read/write > LV Creation host, time , > LV Status available > # open 1 > LV Size 2.79 GiB > Current LE 715 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:3 > > --- Logical volume --- > LV Path /dev/localhost/swap_1 > LV Name swap_1 > VG Name localhost > LV UUID pJlSwq-fmd6-sDck-XYOq-QkUs-Zwju-4Y3uSH > LV Write Access read/write > LV Creation host, time , > LV Status available > # open 2 > LV Size 5.67 GiB > Current LE 1452 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:4 > > --- Logical volume --- > LV Path /dev/localhost/tmp > LV Name tmp > VG Name localhost > LV UUID R7OOqW-fNbz-tl44-HVMj-DLG1-vk5K-RzKN0r > LV Write Access read/write > LV Creation host, time , > LV Status available > # open 1 > LV Size 2.37 GiB > Current LE 607 > Segments 2 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:5 > > --- Logical volume --- > LV Path /dev/localhost/home > LV Name home > VG Name localhost > LV UUID Fdteuo-czY4-O1JA-BmNc-BONn-hldx-ygCvCS > LV Write Access read/write > LV Creation host, time , > LV Status available > # open 1 > LV Size 261.00 GiB > Current LE 66816 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 254:6 > > --- Physical volumes --- > PV Name /dev/mapper/sda5_crypt > PV UUID EYwQCA-is4K-hbWq-RzZ6-HuMB-PxOU-MOCnBS > PV Status allocatable > Total PE / Free PE 76249 / 1871 > > > > > You likely will obtain some specific useful suggestions for moving > > forward that do not involve reinstallation. > > > > I hope so. Even now things are much better than on the upgrade day :-) > > > I have a (now virtual) image of a machine that began life as Debian 1.3 > > (Bo) and has been upgraded, now, through 11.3, the current release, with > > an Oracle 8.0.5 DBMS that was installed around . The upgrades ultimately > > finished satisfactorily, although were occasional bumps in the road. > > > > Funny way to do it. I wonder how your (probable) hardware changes liked > the virtual image (and its upgrades). No complaints?
> As my laptop is 11-year old now, I do not plan to make any hardware > changes, by means of adding RAM or like. Just wonder to see its > behaviour with newer OS's :-) I recommend you don't use the Gnome3 desktop because it is so heavyweight, I actually use the Mate Desktop, a fork of Gnome2. You can also uninstall doc packages and unused linux-image and linux-header packages. To shrink your LVM logical volume, take a look at [0] specifically the section: Resizing a Logical Volume, but first make a backup of your data! [0] https://www.howtogeek.com/howto/40702/how-to-manage-and-use-lvm-logical-volume-management-in-ubuntu/ -- Lic. Guillermo Galeano Fernández