Re: [atomic-devel] docker storage LVM thin pool

[Dusty Mabe <dusty dustymabe com>]

On 06/05/2018 03:39 AM, arnaud gaboury wrote:
> I followed the various guides to create a LVM thin pool storage volume using the helper script container-storage-setup.
> 
> Here is the result:
> 
> ------------------------
> # lsblk
> NAME                          MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> sr0                            11:0    1  492K  0 rom 
> vda                           252:0    0   20G  0 disk
> ├─vda1                        252:1    0    1G  0 part /boot
> └─vda2                        252:2    0   19G  0 part
>   └─atomicos-root             253:0    0   19G  0 lvm  /sysroot
> vdb                           252:16   0  100G  0 disk
> ├─dockervg-docker--pool_tmeta 253:1    0  104M  0 lvm 
> │ └─dockervg-docker--pool     253:3    0 99.8G  0 lvm 
> └─dockervg-docker--pool_tdata 253:2    0 99.8G  0 lvm 
>   └─dockervg-docker--pool     253:3    0 99.8G  0 lvm 
> ---------------------------------
> 
> with this configuration file:
> 
> ---------------------------------
> # cat /etc/sysconfig/docker-storage-setup
> VG=dockervg

Here you are telling container-storage-setup to create a new VG
called dockervg.


> GROWPART=enable
> AUTO_EXTEND_POOL=enable
> MIN_DATA_SIZE=8G
> POOL_AUTOEXTEND_THRESHOLD=60
> POOL_AUTOEXTEND_PERCENT=10
> --------------------------------------
> 
> and this setup:
> 
> ---------------------
> # cat /etc/sysconfig/docker-storage     
> DOCKER_STORAGE_OPTIONS="--storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/dockervg-docker--pool --storage-opt dm.use_deferred_removal=true --storage-opt dm.use_deferred_deletion=true "
> -----------------------
> 
> Now I would like to extend the atomicos VG with adding the /dev/vdb physical volume, but I have an error:
> 
> ---------------------------
>  # pvs
>  PV         VG       Fmt  Attr PSize    PFree
>  /dev/vda2  atomicos lvm2 a--   <19.00g    0
>  /dev/vdb   dockervg lvm2 a--  <100.00g    0
> # vgextend atomicos /dev/vdb
>   Can't open /dev/vdb exclusively.  Mounted filesystem?
> ------------------
> 
> What am I doing wrong? How do you guys extend the atomic root with the storage volume?

you can see from the output /dev/vdb is already part of the dockervg
volume group, so you can't add it to the atomicos volume group.

Dusty