Subject: Re: [vserver] vhashify not working? - 2.6.27.14-vs2.3.0.36.4
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Thu, 2 Apr 2009 13:04:03 +0200

On Tue, Mar 31, 2009 at 09:41:06AM -0400, John A. Sullivan III wrote:
> On Tue, 2009-03-31 at 08:40 +0000, Christoph Lukas wrote:

[stuff zapped]

> Yes, the numbers match and they also match the size of the space
> consumed on the thinly provisioned ZFS zvol on which they reside 
> (28.1 GB):

there is no attribute support for ZFS, and thus
there is no barrier and no CoW-link breaking
available either ... your options are:

 - sponsor development for ZFS/xattrs
 - have immutable hardlinks without CoW link breaking
 - move to a supported filesystem

best,
Herbert

> [root@vd01 ~]# du -sch /vservers/*
> 4.4G    /vservers/cle
> 2.2G    /vservers/gssstation
> 2.2G    /vservers/jasstation
> 1.4G    /vservers/jintra
> 16K     /vservers/lost+found
> 1.4G    /vservers/mintra
> 1.4G    /vservers/mlapo
> 1.4G    /vservers/simple
> 1.4G    /vservers/smcc
> 1.4G    /vservers/tkee
> 1.4G    /vservers/tvan
> 1.4G    /vservers/vdb
> 1.9G    /vservers/vdb2
> 1.4G    /vservers/vde
> 1.1M    /vservers/vetc
> 23G     total
> 
> I am guessing this may also affect my memory usage.  Does VServer use
> the hashify information to determine whether a binary being called into
> memory already exists? Thanks - John
> -- 
> John A. Sullivan III
> Open Source Development Corporation
> +1 207-985-7880
> jsullivan@opensourcedevel.com
> 
> http://www.spiritualoutreach.com
> Making Christianity intelligible to secular society