Score:0

extending an exsiting lvm

bo flag

hello im trying to extend an exsistant lvm /omics/tools to have more space right now it only have a maximum of 5t i want to increase it by 10 df -h shows:

    --- Logical volume ---
  LV Path                /dev/omics/homes
  LV Name                homes
  VG Name                omics
  LV UUID                FwPLkd-epKL-DTYv-Oqdz-svqY-ETM1-DPZq87
  LV Write Access        read/write
  LV Creation host, time bright90, 2020-11-06 18:35:16 +0100
  LV Status              available
  # open                 1
  LV Size                <26.20 TiB
  Current LE             6866944
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     4096
  Block device           253:1

  --- Logical volume ---
  LV Path                /dev/omics/tools
  LV Name                tools
  VG Name                omics
  LV UUID                qkXFaD-YNuT-rswO-jui2-AcpA-ySiA-xj8PL5
  LV Write Access        read/write
  LV Creation host, time bright90, 2020-11-06 18:35:57 +0100
  LV Status              available
  # open                 1
  LV Size                1.00 TiB
  Current LE             262144
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     4096
  Block device           253:2

  --- Logical volume ---
  LV Path                /dev/omics/projects
  LV Name                projects
  VG Name                omics
  LV UUID                cdqxNw-r8tI-rM0C-it14-nz07-28eO-Bc9ojM
  LV Write Access        read/write
  LV Creation host, time bright90, 2020-11-06 18:36:32 +0100
  LV Status              available
  # open                 1
  LV Size                5.23 TiB
  Current LE             1372163
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     4096
  Block device           253:3

fdisk -l shows:

Disk /dev/sda: 446.63 GiB, 479554568192 bytes, 936630016 sectors
Disk model: PERC H330 Mini
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: dos
Disk identifier: 0x66fd4a80

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sda1  *        4096   2101247   2097152     1G 83 Linux
/dev/sda2        2103296  35657727  33554432    16G 82 Linux swap / Solaris
/dev/sda3       35659776 936630015 900970240 429.6G 83 Linux


Disk /dev/sdb: 116.43 TiB, 127999999475712 bytes, 249999998976 sectors
Disk model: ME4
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes


Disk /dev/sdc: 116.43 TiB, 127999999475712 bytes, 249999998976 sectors
Disk model: ME4
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes


Disk /dev/mapper/mpatha: 116.43 TiB, 127999999475712 bytes, 249999998976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes


Disk /dev/mapper/omics-homes: 26.2 TiB, 28802050686976 bytes, 56254005248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes


Disk /dev/mapper/omics-tools: 1 TiB, 1099511627776 bytes, 2147483648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes


Disk /dev/mapper/omics-projects: 5.24 TiB, 5755268759552 bytes, 11240759296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes

df -h shows:

Filesystem                  Size  Used Avail Use% Mounted on
udev                         47G     0   47G   0% /dev
tmpfs                       9.3G   11M  9.3G   1% /run
/dev/sda3                   430G  141G  289G  33% /
tmpfs                        47G     0   47G   0% /dev/shm
tmpfs                       5.0M     0  5.0M   0% /run/lock
tmpfs                        47G     0   47G   0% /sys/fs/cgroup
/dev/sda1                  1007M  385M  572M  41% /boot
/dev/mapper/omics-projects  1.0T  883G  142G  87% /omics/projects
/dev/mapper/omics-tools     1.0T  784G  241G  77% /omics/tools
/dev/mapper/omics-homes      27T  3.7T   23T  15% /omics/homes
192.168.100.204:/backups     60T  8.6T   52T  15% /backups
tmpfs                       9.3G     0  9.3G   0% /run/user/0
tmpfs                       9.3G     0  9.3G   0% /run/user/1004

what im planning to do is extending the lvm by doing

lvextend -l +10000G /dev/omics/tools

but before that do i need to increase the size of omics-tools from /dev/mapper/omics-tools or i dont need that

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.