I have a lxc container named:
It has 1.1 TB of storage allocated and out of that 708GB is consumed.
df -h output when run inside the container:
Filesystem Size Used Avail Use% Mounted on
/dev/loop25 1.1T 708G 331G 69% /
none 492K 4.0K 488K 1% /dev
udev 63G 0 63G 0% /dev/fuse
tmpfs 100K 0 100K 0% /dev/lxd
/dev/nvme0n1p2 1.9T 1.4T 391G 79% /dev/nvidia2
tmpfs 100K 0 100K 0% /dev/.lxd-mounts
tmpfs 63G 0 63G 0% /dev/shm
tmpfs 13G 220K 13G 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 63G 0 63G 0% /sys/fs/cgroup
tmpfs 6.4G 0 6.4G 0% /run/user/1001
As you can see there is 300+ GB available.
But for some reason when I copy a small file (500MB size) from a directory to new dir inside container, I get the error:
No space left on device
This is happening when I create or download a simple 100MB file as well.
Not sure what’s the issue as the storage is there in the container as well on the server.
Please find below some additional information on the volume:
lxc storage info vol-ce9e2a76
space used: 707.75GiB
total space: 1.01TiB
lxc storage show vol-ce9e2a76
Looking forward to getting this resolved quickly. Thanks.
How are you copying that file? Is it done inside the container or through
lxc file push?
Can you show
lxc storage volume show for that volume?
lxc storage volume show
I tried copying data from one directory to another within the container. Basically, it is not able to write any new files either during copy or download using wget or even using fallocate command because it thinks there is not enough storage available.
lxc storage volume show vol-ce9e2a76 data
Error: Storage pool volume not found
How did you create
vol-ce9e2a76? Something doesn’t look quite right here. The location of the
/var/snap/lxd/common/lxd/disks/vol-ce9e2a76.img file suggests this is a BTRFS storage pool, and yet you appear to be passing the entire storage pool into an instance as a disk device. I’m not sure that is supported.
Please can you show me
lxc config show lxc-ce9e2a76 --expanded please, in case I am misreading this.
@tomp sorry for the delay.
I think it is being passed as a root volume to the container. Not sure if it is getting added as a disk device. We simply add the volume to container profile.
Please find below the output for:
lxc config show lxc-ce9e2a76 --expanded
image.description: LXC Image V3
OK thats fine makes sense now. The naming of the pool as “vol-…” confused me there, as its not a volume (in the LXD sense anyway).
Can you show me the output of
sudo losetup on the host please?
Also how much disk space do you have on the partition that holds
@tomp sorry for the delayed replies. I have 2TB disk out of which 300GB is available on root partition i.e “/” path.