[Starlingx-discuss] controller filesystem
Sun, Austin
austin.sun at intel.com
Thu Nov 21 14:20:00 UTC 2019
Hi Volker:
>From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html
You can probably the command line to change the size of docker lv
Thanks.
BR
Austin Sun.
From: von Hoesslin, Volker <Volker.Hoesslin at swsn.de>
Sent: Thursday, November 21, 2019 9:20 PM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] controller filesystem
hi,
i trying to import some existing qcow2 images into my new installed STX 2.0.
openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar"
all works fine, the image are available.
now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point
/dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker
increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself?
btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error:
Error: backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request.
- see attachment -
how can i increase the backup size to handle this error?!
greez & thx, volker...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191121/29cc54f5/attachment.html>
More information about the Starlingx-discuss
mailing list