modified vz_root and vz_private confuses frontend web

[muzzol]

hi,

i know is unsupported:

http://forum.proxmox.com/threads/6195-vzquota-doesn-t-honour-VE_PRIVATE

but i would know if i must open a bug for this.

i've configured some containers on a samba mounted resource. in my 134.conf i have:

VE_ROOT="/mnt/samba/vzbase/root/134"
VE_PRIVATE="/mnt/samba/vzbase/private/134"

and everything seems to be fine except CPU and Memory bars on frontend.

is there any (unsupported) workaround for this?

is there any other issues to be aware?

 

[dietmar]

OpenVZ only support Quota one ext3 (not on samba/cifs)

 

[muzzol]

ok,

so i assume that if mounted fs is an iscsi volume it can be used that way.

i'm i correct?

 

[dietmar]

don't know, we do not test that.

 

[muzzol]

ok, i'll try that and i'll update this thread with results.

anyway, do you have any plans regarding external/additional storage devices for openvz?

seems to be a quite common issue around forums and lists and i'm not sure the amount of coding effort it requires.

 

[dietmar]

anyway, do you have any plans regarding external/additional storage devices for openvz?

no (no plans)