Problem to configure persistent storage on LV

[oldvladko]

Hello,

I’ve tried to configure custom persistent storage using this guide https://www.uyuni-project.org/uyuni-docs/en/uyuni/installation-and-upgrade/container-deployment/uyuni/server-deployment-uyuni.html#_container_host_general_requirements . For the storage-disk-device and database-disk-device I wat to user both devices on LV . I think to have both /var/lib/containers/storage/volumes and /var/lib/containers/storage/volumes/var-pgsql on LV is good idea if it would be required to extend them in future.

When ran the mgr-storage-server command I received the following error below :

mgr-storage-server /dev/vg-storage/lvstorage /dev/vg-db/lvdb

--> Checking disk for content signature
--> Creating partition on disk /dev/dm-0
--> Creating xfs filesystem
Error: xfs filesystem setup failed: Error accessing specified device /dev/dm-01: No such file or directory
Usage: mkfs.xfs
/* blocksize / [-b size=num]
/ config file / [-c options=xxx]
/ metadata / [-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1,
inobtcount=0|1,bigtime=0|1]
/ data subvol / [-d agcount=n,agsize=n,file,name=xxx,size=num,
(sunit=value,swidth=value|su=num,sw=num|noalign),
sectsize=num
/ force overwrite / [-f]
/ inode size / [-i perblock=n|size=num,maxpct=n,attr=0|1|2,
projid32bit=0|1,sparse=0|1,nrext64=0|1]
/ no discard / [-K]
/ log subvol / [-l agnum=n,internal,size=num,logdev=xxx,version=n
sunit=value|su=num,sectsize=num,lazy-count=0|1]
/ label / [-L label (maximum 12 characters)]
/ naming / [-n size=num,version=2|ci,ftype=0|1]
/ no-op info only / [-N]
/ prototype file / [-p fname]
/ quiet / [-q]
/ realtime subvol / [-r extsize=num,size=num,rtdev=xxx]
/ sectorsize / [-s size=num]
/ version */ [-V]
devicename
is required unless -d name=xxx is given.
is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
is xxx (512 byte blocks).

rpm -qf /usr/bin/mgr-storage-server

uyuni-storage-setup-server-5.0.2-2.1.uyuni.x86_64

When created the LVs both /dev/vg-storage/lvstorage and /dev/vg-db/lvdb point to /dev/dm-0 and /dev/dm-1 accordingly:

ls -l /dev/vg-storage/lvstorage

lrwxrwxrwx. 1 root root 7 Sep 15 20:20 /dev/vg-storage/lvstorage -> ../dm-0

ls -l /dev/vg-db/lvdb

lrwxrwxrwx. 1 root root 7 Sep 15 20:21 /dev/vg-db/lvdb -> ../dm-1

If the mgr-storage-server can accept LV as device ?

Any idea how to fix the problem please ?

Thanks.