activating a lvm in a group

sniper8752 · 12-17-2020, 11:28 AM

I am trying to activate a lvm in a group. In the group, there are a total of 3 lvms. This one is not mounting though:

Code:

  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                GSlWfw-Y3aH-6C7l-iJ62-rqJD-TVQV-KxRO3y
  LV Write Access        read/write
  LV Creation host, time proxmox, 2020-04-04 20:07:21 -0400
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 17
  LV Size                <794.29 GiB
  Allocated pool data    19.58%
  Allocated metadata     1.17%
  Current LE             203337
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4

I look in /dev/pve, and "data" is not in there. The two others in the group show up.

smallpond · 12-17-2020, 11:42 AM

What's the output of:

Code:

lsblk -a -fs

sniper8752 · 12-17-2020, 11:49 AM

Code:

NAME                                                         FSTYPE      LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sdb1                                                                                                                                 
└─sdb                                                                                                                                
sdb2                                                         vfat              13AC-6EE2                               510.7M     0% /boot/efi
└─sdb                                                                                                                                
sdc1                                                         iso9660     PVE   2020-05-10-19-27-04-00                                
└─sdc                                                        iso9660     PVE   2020-05-10-19-27-04-00                                
sdc2                                                         vfat        PVE   6DC7-2009                                             
└─sdc                                                        iso9660     PVE   2020-05-10-19-27-04-00                                
sdc3                                                         hfsplus     PVE   2020-05-10-19-27-04-00                                
└─sdc                                                        iso9660     PVE   2020-05-10-19-27-04-00                                
sdc4                                                         iso9660     PVE   2020-05-10-19-27-04-00                                
└─sdc                                                        iso9660     PVE   2020-05-10-19-27-04-00                                
sr0                                                                                                                                  
pve-swap                                                     swap              82b037c1-26b1-4e55-a6db-70c1dcb73db3                  [SWAP]
└─sdb3                                                       LVM2_member       gBYPnI-37nh-yaae-DdQ9-I2my-mh1G-LsC51C                
  └─sdb                                                                                                                              
pve-root                                                     ext4              d1e46b00-86f1-48c5-9b64-09a70abb68f3     35.3G    57% /
└─sdb3                                                       LVM2_member       gBYPnI-37nh-yaae-DdQ9-I2my-mh1G-LsC51C                
  └─sdb                                                                                                                              
pve-data                                                                                                                             
└─pve-data-tpool                                                                                                                     
  ├─pve-data_tmeta                                                                                                                   
  │ └─sdb3                                                   LVM2_member       gBYPnI-37nh-yaae-DdQ9-I2my-mh1G-LsC51C                
  │   └─sdb                                                                                                                          
  └─pve-data_tdata                                                                                                                   
    └─sdb3                                                   LVM2_member       gBYPnI-37nh-yaae-DdQ9-I2my-mh1G-LsC51C                
      └─sdb                                                                                                                          
pve-vm--102--disk--0                                                                                                                 
└─pve-data-tpool                                                                                                                     
  ├─pve-data_tmeta                                                                                                                   
  │ └─sdb3                                                   LVM2_member       gBYPnI-37nh-yaae-DdQ9-I2my-mh1G-LsC51C                
  │   └─sdb                                                                                                                          
  └─pve-data_tdata                                                                                                                   
    └─sdb3                                                   LVM2_member       gBYPnI-37nh-yaae-DdQ9-I2my-mh1G-LsC51C                
      └─sdb

smallpond · 12-17-2020, 12:13 PM

So pve-data does not have a filesystem. It is part of a thin pool supporting thin volumes. See lvmthin documentation. I'm not familiar with thin pools, but it looks like your pve-swap and pve-root lvms are using the thin pool.

berndbausch · 12-17-2020, 02:11 PM

Quote:

Originally Posted by smallpond

It is part of a thin pool supporting thin volumes.

It is a thin pool, I'd say. Which means that it is not supposed to have a filesystem or to be mounted.

To understand which volume is thin or not, the output of the lvs command would be helpful.

Quote:

I am trying to activate a lvm in a group. In the group, there are a total of 3 lvms. This one is not mounting though:

As said, this logical volume has no filesystem and, since it's a thin pool, is not supposed to have one anyway. It is activated, as far as I can see (status: available).

sniper8752 · 12-17-2020, 02:23 PM

LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-aotz-- <794.29g 19.74 1.17
root pve -wi-ao---- 96.00g
swap pve -wi-ao---- 8.00g
vm-102-disk-0 pve Vwi-aotz-- 32.00g data 20.98

berndbausch · 12-17-2020, 04:33 PM

Quote:

Originally Posted by sniper8752

Code:

LV                             VG  Attr       LSize    Pool Origin    Data%  Meta%  Move Log Cpy%Sync Convert
 data                          pve twi-aotz-- <794.29g                19.74  1.17                            
  root                         pve -wi-ao----   96.00g                     
  swap                         pve -wi-ao----    8.00g                                                           
  vm-102-disk-0                pve Vwi-aotz--   32.00g data     20.98

vm-102-disk-0 is a thinly provisioned volume as indicated by the V flag and its pool parameter.

So the question is, why do you want to mount data? As said earlier, it is a thin pool. Using it as a volume for a filesystem would destroy the pool and thereby vm-102-disk-0.

sniper8752 · 12-18-2020, 07:04 AM

It is a 1 TB drive, and I have just about used up the 100GB allocated. I wanted to expand into this thin pool. So it sounds like there is no way to do this without loss of data?

berndbausch · 12-18-2020, 03:48 PM

The thin pool has a size of 800GB, of which 20% are used. You can create plenty of additional logical volumes from this pool, or increase the size of the vm-102-disk-0 volume.

I don't understand what you want to expand.