[openvps-dev] tagxid

[Roderick A. Anderson]

On Fri, 12 Aug 2005, Gregory (Grisha) Trubetskoy wrote:

> 
> Well... Without tagxid you will not be able to restrict disk space usage 
> per-vps, and mounting your / with tagxid is probably not a good idea 
> since a non VServer kernel will not be able to mount it.

Well this is just for in-house use so limiting disk space usage isn't an 
issue.  But when I (re)build a couple of others I'll keep this in mind.  
In fact the others do have seperate /vservers partitions.  It is just this 
system that doesn't.  An rush to install the OS and I don't have enough 
time to go back and redo it.

> Generally, I've never tested OpenVPS on a system where /vservers was not a 
> spearate partition. Definitely the ovbackup script will not like it 
> because it assumes it's a "dumpable" mount point.

I'll probably disable this then.

> One workaround may be to create a loop-mounted filesystem, e.g for 1GB 
> (you'll probably need more than that though).
> 
> # dd if=/dev/zero of=/VSERVERS bs=1M count=1000
> # losetup /dev/loop0 /VSERVERS
> # mkfs.ext3 /dev/loop0
> # mount -o tagxid /dev/loop0 /vservers
> 
> If you need for it to mount on startup, you'll need write an init script 
> for it, or as a hack stick it rc.sysinit or something....

Sounds fun but probably not a good idea for this situation.

Thanks for the quick response.  I now also know that tagxid is Vserver 
specific.


Rod
-- 
    "Open Source Software - You usually get more than you pay for..."
     "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"