Subject: Re: [vserver] Possible Hashify Corruption
From: Gordan Bobic <gordan@bobich.net>
Date: Tue, 19 Oct 2010 09:20:07 +0100

Ghislain wrote:
>> For completenes, the userspace packages I use are:
>>
>> util-vserver-lib-0.30.215+svn2847-143596525.fc12.x86_64
>> util-vserver-build-0.30.215+svn2847-143596525.fc12.x86_64
>> util-vserver-core-0.30.215+svn2847-143596525.fc12.x86_64
>> util-vserver-0.30.215+svn2847-143596525.fc12.x86_64
>> util-vserver-sysv-0.30.215+svn2847-143596525.fc12.x86_64
>>
>> The kernel is 2.6.30.10-vs2.3.0.36.14-pre8.
> 
> hi,
> 
> using vserver util from stable with 2.3 experimental kernel patch will
> lead to troubles. You need to have a userland that match your kernel or
> strange thing will happen. With 2.3 you MUST use 0.30.216, the latest
> the better.

I don't see 0.30.216 here yet:
http://ftp.linux-vserver.org/pub/utils/util-vserver/

> john use the right combo of utils/kernel but you do not. I think this
> can explain your weird issues (perhaps)

I would have thought the hashify feature is pretty user-space (check 
hashes, and create hard-links, it's pretty much a job for a bash 
script), but I did find this:
http://people.linux-vserver.org/~dhozac/t/uv-testing/
so I'll do a test with the current kernel and the latest bleeding edge 
user-space.

My main suspect at the moment is an ext4 bug, though. If it doesn't go 
away with the latest kernel and userspace I'll try with ext2 and see if 
that makes the problem go away. But even if it does, this still needs to 
be investigated and the root cause identified, since it verifiably leads 
to file corruption.

Gordan