New features
Lessfs now supports asynchronous master/slave replication. Replication can be enabled and disabled with a simple ‘ echo 1 >/.lessfs/replication/enabled’ where 1 is enabled and 0 is disabled. Lessfs uses CRC32 checksums to ensure data integrity during data transfer between master and slave. See the README.replication file in the distribution for more details. Replication should still be considered alpha code. That said, it works for me. 
Improvements
The background delete/truncation code has stabilized to the point where it will become the default with the next release.
Hi
I am still having problems with my system, starting to suspect harddrive trouble, On high loads (deleting lots of files f.ex) I get these messages in the log:
Sep 26 17:22:06 backup1 lessfs[1680]: delete_inuse: failed to delete read error
Sep 26 17:22:06 backup1 lessfs[1680]: delete_inuse: failed to delete read error
Sep 26 17:22:06 backup1 lessfs[1680]: delete_inuse : failed
Sep 26 17:22:06 backup1 lessfs[1680]: delete_inuse : failed
Could this be due to disk problems ?
Hi Mark, nice news, then, i read in the readme, but i might miss some détails about SLAVE :
To configure lessfs as master the following lines need to
be added to lessfs.cfg:
REPLICATION=masterslave
REPLICATION_PARTNER_IP=xx.xx.xx.xx
REPLICATION_PARTNER_PORT=201
REPLICATION_ROLE=master
So, what about the slave ?
i guess something like
REPLICATION=masterslave
REPLICATION_PARTNER_IP=zz.zz.zz.zz
REPLICATION_PARTNER_PORT=201
REPLICATION_ROLE=slave
?
Gonna try but just wanna be sure
A complete example can be found in the example directory.
REPLICATION=masterslave
REPLICATION_ROLE=slave
REPLICATION_LISTEN_IP=127.0.0.1
REPLICATION_LISTEN_PORT=201
Thx a lot
that’s what happen when making thing with all those phones call non-stop ! So, thx for this fast answer 