Everything at 1% on the proxmox host
The other question still is how to deal with the 100% full LVM and if that has is actually causing the fsck issue/clone problem.
That LVM has 375 GB, 220 of which are taken up by the container's root disk and 50GB by a container template, nothing else. So I...
I have container using a root disk in a thin lvm. At some point today, I got input/output error from docker running in that container. The root disk itself has enough free space, but the thin lvm for that root disk says 100% allocation. Could this be the reason for the I/O errors?
So I tried...
Can't really make heads and tails of that :oops:
The local-lvm I see in the UI (with the 340.90 GB of 375.07 GB reported there) doesn't even appear in that list:
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
vm-101-disk-0...
So there's no way to find out how much space is now actually available on that volume? It says 340.90 GB of 375.07 GB but after having moved out the 50GBs it actually should be more...
Cool :-) Only thing I notice is that the original LVM doesn't gain back the full space of the volume (although I had said "Delete source" for the move)
This is probably an FAQ, but I can't seem to find a straight forward approach for this:
There's a container with a relatively small root disk on a relatively small LVM (on an internal disk)
I successfully added a 2nd lvm for an external SSD following this approach
Now how di I "give" the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.