LXC Inodes

[matthew]

I am installing Directadmin on LXC container. How do I insure there are enough inodes available? As I recall on openvz you could specify this. Also, how can you specify the number of users a container is allowed to have? I believe under Openvz this was called UGID?

 

[dietmar]

I am installing Directadmin on LXC container. How do I insure there are enough inodes available?

We use a separate file system for containers, so there is no such setting.

 

[matthew]

I am assuming that is the *.raw file under images? In past with openvz you could over subscribe disk space. If I set container for 2TB but it only used 80GB on disk I would have that space to use elsewhere when that container did not use it. Is that not the case anymore? That was nice.

Also, if I have container set to only 100GB can I later expand it too 500GB of space? If so will inodes expand as well later?

Thanks.

 

[sigxcpu]

I think that .raw file is sparse, so it doesn't take so much space on disk.
If you want easy growing the container disk size, use ZFS. PVE4 integrated ZFS beautifully.

 

[wbumiller]

You can use pct resize later on. Eg.

pct resize 100 rootfs +200G

increases the ct's root disk by 200 gigs

 

[matthew]

I see this.

ls -la /var/lib/vz/images/100
-rw-r----- 1 root root 214748364800 Oct 20 09:45 vm-100-disk-1.raw

Does that mean when I create a 200GB container it will take up 200GB disk space?

Strange that when I look at backup it looks like this.

ls -ls /backups/dump
163936 -rw-r--r-- 1 root root 167869472 Oct 19 17:25 vzdump-lxc-100-2015_10_19-17_24_44.tar.gz

Stranger yet.

du -h /var/lib/vz/images/100
707M /var/lib/vz/images/100

 

[dietmar]

Does that mean when I create a 200GB container it will take up 200GB disk space?

We create sparse files by default, but it can take up to 200GB once you start writing data inside the container.