[Gluster-users] Write-behind breaks Mercurial

[Simon Litchfield]

Hi all

It seems Mercurial doesn't work with "write behind" on. Any ideas?

With write-behind --

root at dj1:~/mnt# gluster volume set conf performance.write-behind on
Set volume successful
root at dj1:~/mnt# hg clone http://projects.unbit.it/hg/uwsgi
destination directory: uwsgi
requesting all changes
adding changesets
transaction abort!
rollback completed
abort: integrity check failed on 00changelog.i:24!

Without write-behind --

root at dj1:~/mnt# gluster volume set conf performance.write-behind off
Set volume successful
root at dj1:~/mnt# hg clone http://projects.unbit.it/hg/uwsgi
destination directory: uwsgi
requesting all changes
adding changesets
adding manifests
adding file changes
added 1169 changesets with 3532 changes to 332 files
updating to branch default
278 files updated, 0 files merged, 0 files removed, 0 files unresolved

Shouldn't the write behind cache be reading unwritten data before it hits the disk? 

Cheers
Simon