Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 173527

Proxmox 3.x openVZ creating a new mountpoint

$
0
0
Hi, Could anyone enlighten me please and or point me to the right documentation where I could read up on something that I haven't seen on Proxmox 2.x.

I know its not a strictly supported way but I did run my openvz containers on zfs native (compressed and deduplicated) for quite some while and I never ever had any issue on Proxmox 2.x.
I don't have a real issue now but I spotted after a rebuild that my containers are spawning another mount point.

I checked up and its not a link but its the same directories and contents.

/zfs-data/Proxmox/private/105 is where I have the real data.

when starting the vz it takes significantly longer (about 1 - 2 minutes) and I get

zfs-data 32G 128K 32G 1% /zfs-data
zfs-data/Proxmox 115G 84G 32G 73% /zfs-data/Proxmox

/zfs-data/Proxmox//private/105 4.0G 1.4G 2.7G 33% /var/lib/vz/root/105
none 192M 4.0K 192M 1% /var/lib/vz/root/105/dev
none 192M 0 192M 0% /var/lib/vz/root/105/dev/shm

/var/lib/vz/root/105 is not a hard or softlink and I assume it must be something brand new on openVZ or proxmox3.

Could anyone hint me please or tell where and what to look for to understand why? thanks

Viewing all articles
Browse latest Browse all 173527

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>