Thanks for this Stéphane, it looks like none of the instances on this host have rootfs linked… Also all other container have the same “Hostid”:1000000 in idmap config.
Also, all of the lvm commands report nothing which is quite concerning.
The full story is:
- an attempt was made to expand the storage of the container with
lxc config device set omeka-s root size 20GB - the container failed to restart (it never shut down fully, but services stopped)
- the container was force stoped
- on restart the resize failed
-
lxc config device unset omeka-s root sizewas run in an attempt to cancel the resize which also failed - the volume for the container disappear from lvm commands
-
ln -s ../dm-14 containers_omeka--swas run to re-establish the link to the lvm device - the container booted normally
- attempt was made to publish the container to create a backup
- root disk space became low so publish was cancelled
- container list uif/gui shift info
- current state
How do I access the rootfs from the host? They don’t appear to be mounted anywhere.
Is this fuidshift? GitHub - Mic92/fuidshift: Move Filesystem ownership into other subordinated uid ranges
Output from lvmdump appears to have the relevant entries. Should I just restart the host to recover state?
I will certainly update lxd next opportunity, this is somewhat an inherited situation. edit : it appears to have been set up with guidance from this : LXD on Centos 7 is LXD now stable on centos 7?
Many thanks,
Simon