LINUX.ORG.RU

Разбивка диска по умолчанию в Ubuntu Server 20.04.3 LTS

 , ,


1

1

Всем привет! Проясните мне пожалуйста такую ситуацию - исталирую Ubuntu Server 20.04.3 LTS на диск 32 Гб. В процессе инсталяции настройки, касающиеся диска, оставил по умолчанию.

После установки вижу следующую картину:

xxxx:~$ sudo lsblk

NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0                       7:0    0 55.4M  1 loop /snap/core18/2128
loop1                       7:1    0 61.9M  1 loop /snap/core20/1270
loop2                       7:2    0 32.3M  1 loop /snap/snapd/12704
loop3                       7:3    0 43.3M  1 loop /snap/snapd/14295
loop4                       7:4    0 70.3M  1 loop /snap/lxd/21029
loop5                       7:5    0 67.2M  1 loop /snap/lxd/21835
loop6                       7:6    0 55.5M  1 loop /snap/core18/2284
sda                         8:0    0   32G  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    1G  0 part /boot
└─sda3                      8:3    0   31G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0 15.5G  0 lvm  /
sr0                        11:0    1  1.2G  0 rom

Т.е. правильно я понимаю, что из 32 Гб реально используется только примерно половина, а половина sda3 вообще не распределена и не используется?

Зачем так сделано? Можно ли использовать всё пространство тома sda3?



Последнее исправление: Garik368 (всего исправлений: 1)

Ответ на: комментарий от Vsevolod-linuxoid
xxxx:~$ df -hT
Filesystem                        Type      Size  Used Avail Use% Mounted on
udev                              devtmpfs  1.9G     0  1.9G   0% /dev
tmpfs                             tmpfs     394M  1.3M  392M   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv ext4       16G  7.2G  7.3G  50% /
tmpfs                             tmpfs     2.0G     0  2.0G   0% /dev/shm
tmpfs                             tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                             tmpfs     2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/sda2                         ext4      976M  108M  801M  12% /boot
/dev/loop0                        squashfs   56M   56M     0 100% /snap/core18/2128
/dev/loop2                        squashfs   33M   33M     0 100% /snap/snapd/12704
/dev/loop1                        squashfs   62M   62M     0 100% /snap/core20/1270
/dev/loop4                        squashfs   71M   71M     0 100% /snap/lxd/21029
/dev/loop3                        squashfs   44M   44M     0 100% /snap/snapd/14295
/dev/loop6                        squashfs   56M   56M     0 100% /snap/core18/2284
/dev/loop5                        squashfs   68M   68M     0 100% /snap/lxd/21835
tmpfs                             tmpfs     394M     0  394M   0% /run/user/1000

xxxx:~$ df -hi
Filesystem                        Inodes IUsed IFree IUse% Mounted on
udev                                481K   476  480K    1% /dev
tmpfs                               492K   840  491K    1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   992K  104K  889K   11% /
tmpfs                               492K     4  492K    1% /dev/shm
tmpfs                               492K     7  492K    1% /run/lock
tmpfs                               492K    18  492K    1% /sys/fs/cgroup
/dev/sda2                            64K   312   64K    1% /boot
/dev/loop0                           11K   11K     0  100% /snap/core18/2128
/dev/loop2                           474   474     0  100% /snap/snapd/12704
/dev/loop1                           12K   12K     0  100% /snap/core20/1270
/dev/loop4                          1.6K  1.6K     0  100% /snap/lxd/21029
/dev/loop3                           479   479     0  100% /snap/snapd/14295
/dev/loop6                           11K   11K     0  100% /snap/core18/2284
/dev/loop5                           796   796     0  100% /snap/lxd/21835
tmpfs                               492K    22  492K    1% /run/user/1000

хххх:~$ sudo pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda3
  VG Name               ubuntu-vg
  PV Size               <31.00 GiB / not usable 0
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              7935
  Free PE               3968
  Allocated PE          3967
  PV UUID               9v3Olw-5cTX-CkEj-Xisy-xpnH-tedD-Lr69on

xxxx:~$ sudo vgdisplay
  --- Volume group ---
  VG Name               ubuntu-vg
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  2
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               <31.00 GiB
  PE Size               4.00 MiB
  Total PE              7935
  Alloc PE / Size       3967 / <15.50 GiB
  Free  PE / Size       3968 / 15.50 GiB
  VG UUID               An7W8W-DjI0-4Iqx-JAZp-yOL4-an3f-yXwZqj

xxxx:~$ sudo lvdisplay
  --- Logical volume ---
  LV Path                /dev/ubuntu-vg/ubuntu-lv
  LV Name                ubuntu-lv
  VG Name                ubuntu-vg
  LV UUID                SAkoeO-eoxv-wGdj-g8at-JiOJ-6pgB-tiCufh
  LV Write Access        read/write
  LV Creation host, time ubuntu-server, 2022-01-16 20:39:37 +0300
  LV Status              available
  # open                 1
  LV Size                <15.50 GiB
  Current LE             3967
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

xxxx:~$ sudo fdisk -l
Disk /dev/loop0: 55.45 MiB, 58130432 bytes, 113536 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: 61.93 MiB, 64913408 bytes, 126784 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: 32.3 MiB, 33865728 bytes, 66144 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: 43.28 MiB, 45371392 bytes, 88616 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: 70.32 MiB, 73728000 bytes, 144000 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: 67.25 MiB, 70508544 bytes, 137712 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: 55.52 MiB, 58204160 bytes, 113680 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/sda: 32 GiB, 34359738368 bytes, 67108864 sectors
Disk model: QEMU HARDDISK
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: 91A76E78-A390-4144-BAA0-ACDE3A97721F

Device       Start      End  Sectors Size Type
/dev/sda1     2048     4095     2048   1M BIOS boot
/dev/sda2     4096  2101247  2097152   1G Linux filesystem
/dev/sda3  2101248 67106815 65005568  31G Linux filesystem


Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 15.51 GiB, 16638803968 bytes, 32497664 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

Garik368
() автор топика
Ответ на: комментарий от anonymous

спасибо, ситуация проясняется)

🐞 https://bugs.launchpad.net/subiquity/+bug/1785321

приведу цитату, может ещё кому-то пригодиться

The reason only 4GiB is allocated to the root file-system is that the remaining space is there to be allocated for other purposes by the system administrator.

E.g. The administrator may want to allocated separate block devices to host virtual machine or container images, and so on.

To view the free space in the parent Volume Group (VG) look at the Free PE: (Physical Extents):

$ sudo vgdisplay

To grow an existing Logical Volume (LV) and the (ext*) file-system within it to use 25% of the Free PE:

$ sudo lvextend -l 25%FREE VG_NAME/LV_NAME
$ sudo resize2fs /dev/mapper/VG_NAME-LV_NAME

See "man lvextend" for more options.

To create additional LVs do e.g:

$ sudo lvcreate -L 6G -n LV_NEW_NAME VG_NAME
$ sudo mkfs.ext /dev/mapper/VG_NAME-LV_NEW_NAME
$ sudo mkdir /mnt/more_storage
$ sudo mount /dev/mapper/VG_NAME-LV_NEW_NAME /mnt/more_storage
Garik368
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.