Proxmox doesn't store CTs on a different storage

[XATRIX]

Hi, i've found a strange behavior of a Proxmox VE. And it repeats on multiple instances of a Proxmox.
When i try to create a new CT, i choose 'storage' as a storage device to place CTs root&private files on, but it always puts it on a default one 'local'.
I tried to move these files manually to /mnt/private /mnt/root , and change related config files but it seems like it doesn't make sens, cause i even can't start CTs. Something like problems with quotas or something like this.

My 'storage' device is a manually created mdraid1+LVM+XFS mounted to /mnt - ~1TB of a disk space.

I also will attach some screenshot and config file of a newly created CT. I didn't change anything, just pasting it as is...

root@ve1-ua:~# cat /etc/vz/conf/100.conf ONBOOT="no" PHYSPAGES="0:512M" SWAPPAGES="0:512M" KMEMSIZE="232M:256M" DCACHESIZE="116M:128M" LOCKEDPAGES="256M" PRIVVMPAGES="unlimited" SHMPAGES="unlimited" NUMPROC="unlimited" VMGUARPAGES="0:unlimited" OOMGUARPAGES="0:unlimited" NUMTCPSOCK="unlimited" NUMFLOCK="unlimited" NUMPTY="unlimited" NUMSIGINFO="unlimited" TCPSNDBUF="unlimited" TCPRCVBUF="unlimited" OTHERSOCKBUF="unlimited" DGRAMRCVBUF="unlimited" NUMOTHERSOCK="unlimited" NUMFILE="unlimited" NUMIPTENT="unlimited" # Disk quota parameters (in form of softlimit:hardlimit) DISKSPACE="5G:5632M" DISKINODES="1000000:1100000" QUOTATIME="0" QUOTAUGIDLIMIT="0" # CPU fair scheduler parameter CPUUNITS="1000" CPUS="1" HOSTNAME="test.test" SEARCHDOMAIN="test" NAMESERVER="8.8.8.8" IP_ADDRESS="192.168.1.100" VE_ROOT="/var/lib/vz/root/$VEID" VE_PRIVATE="/mnt/private/100" OSTEMPLATE="centos-6-standard_6.3-1_i386.tar.gz" root@ve1-ua:~#

 

[dietmar]

When i try to create a new CT, i choose 'storage' as a storage device to place CTs root&private files on, but it always puts it on a default one 'local'.

Why do you think it is on local storage?

Note: /var/lib/vz/root/<vmid> is just a symlink

 

[XATRIX]

Are you sure ?

root@ve2-ua:~# ls -la /var/lib/vz
total 48
drwxr-xr-x 9 root root 4096 Jan 24 14:07 .
drwxr-xr-x 44 root root 4096 Feb 8 23:28 ..
drwxr-xr-x 2 root root 4096 Oct 2 11:38 dump
drwxr-xr-x 2 root root 4096 Feb 10 19:49 images
drwxr-xr-x 2 root root 4096 Feb 11 17:05 lock
drwx------ 2 root root 16384 Jan 24 13:28 lost+found
drwxr-xr-x 5 root root 4096 Feb 10 20:46 private
drwxr-xr-x 5 root root 4096 Feb 10 20:46 root
drwxr-xr-x 5 root root 4096 Jan 24 14:07 template

root@ve2-ua:~# ls -la /var/lib/vz/private/
total 20
drwxr-xr-x 5 root root 4096 Feb 10 20:46 .
drwxr-xr-x 9 root root 4096 Jan 24 14:07 ..
drwxr-xr-x 21 root root 4096 Feb 8 22:23 100
drwxr-xr-x 21 root root 4096 Feb 8 22:23 101
drwxr-xr-x 21 root root 4096 Feb 10 22:50 102

root@ve2-ua:~# ls -la /var/lib/vz/private/101
total 96
drwxr-xr-x 21 root root 4096 Feb 8 22:23 .
drwxr-xr-x 5 root root 4096 Feb 10 20:46 ..
-rw-r--r-- 1 root root 0 Feb 8 22:23 .autofsck
-rw-r--r-- 1 root root 0 Feb 4 23:43 .autorelabel
dr-xr-xr-x 2 root root 4096 Feb 6 15:49 bin
dr-xr-xr-x 3 root root 4096 Feb 6 15:49 boot
drwxr-xr-x 5 root root 4096 Feb 8 22:23 dev
drwxr-xr-x 75 root root 4096 Feb 10 19:03 etc
drwxr-xr-x 2 root root 4096 Feb 8 12:46 home
dr-xr-xr-x 10 root root 4096 Feb 6 15:49 lib
dr-xr-xr-x 7 root root 12288 Feb 6 15:49 lib64
drwxr-xr-x 2 root root 4096 Sep 23 2011 media
drwxr-xr-x 8 root root 4096 Feb 8 17:24 mnt
drwxr-xr-x 2 root root 4096 Sep 23 2011 opt
dr-xr-xr-x 2 root root 4096 Oct 4 23:40 proc
-rw------- 1 root root 1024 Feb 5 13:09 .rnd
dr-xr-x--- 10 root root 4096 Feb 8 21:31 root
dr-xr-xr-x 2 root root 4096 Feb 6 15:49 sbin
drwxr-xr-x 2 root root 4096 Sep 23 2011 selinux
drwxr-xr-x 2 root root 4096 Sep 23 2011 srv
drwxr-xr-x 2 root root 4096 Sep 23 2011 sys
drwxrwxrwt 3 root root 4096 Feb 10 16:47 tmp
drwxr-xr-x 14 root root 4096 Feb 5 14:12 usr
drwxr-xr-x 23 root root 4096 Feb 7 17:52 var

root@ve2-ua:~#

The same server built by the same scheme...

 

[XATRIX]

So, any idea how to fix it ?

 

[dietmar]

So, any idea how to fix it ?

It is not a symbolic link, but a mount point (bind mount).