Hello Jay,
I configured lessfs to work with BerkeleyDB and HamsterDB. They suggest to use one of these over the default Tokyocabinet.
For BerkeleyDB I just modified a few things in the file etc/lessfs.cfg-bdb in the lessfs sources. Please find my configuration below:
# Enable informational messages about compression.
DEBUG = 5
HASHNAME=MHASH_TIGER192
#HASHNAME=MHASH_SHA256
# The (chopped) hashlen in bytes, minimum is 20.
HASHLEN = 24
BLOCKDATA_IO_TYPE=file_io
BLOCKDATA_PATH=/data/dta/blockdata.dta
#BLOCKDATA_IO_TYPE=chunk_io
#BLOCKDATA_PATH=/data/dta/
#
META_PATH=/data/mta
#META_BS=1048576
#
CACHESIZE=512
# Flush data to disk after X seconds.
COMMIT_INTERVAL=10
#
LISTEN_IP=127.0.0.1
LISTEN_PORT=100
# Not more then 2 on most machines.
MAX_THREADS=16
#DYNAMIC_DEFRAGMENTATION on or off, default is off.
DYNAMIC_DEFRAGMENTATION=on
COREDUMPSIZE=2560000000
# Consider SYNC_RELAX=1 or SYNC_RELAX=2 when exporting lessfs with NFS.
SYNC_RELAX=0
# When BACKGROUND_DELETE=on lessfs will spawn a thread to delete
# a file as a background task. This is a recently added feature
# and is therefore disabled by default.
BACKGROUND_DELETE=on
# Requires openssl and lessfs has to be configured with --with-crypto
ENCRYPT_DATA=on
# ENCRYPT_META on or off, default is off
# Requires ENCRYPT_DATA=on and is otherwise ignored.
ENCRYPT_META=off
# You don't like fsck?
ENABLE_TRANSACTIONS=on
# Select a blocksize to fit your needs.
BLKSIZE=131072
COMPRESSION=qlz
#TUNEFORSPEED=yes
#
##### LFS MASTER #####
#REPLICATION=masterslave
#REPLICATION_ROLE=master
###BULK REPLICATION
###REPLICATION_PARTNER_IP=-1
##LFS NATIVE REPLICATION
#REPLICATION_PARTNER_IP=10.10.10.10
#REPLICATION_PARTNER_PORT=101
#MAX_BACKLOG_SIZE=1000000
##### LFS SLAVE #####
#REPLICATION=masterslave
#REPLICATION_ROLE=slave
# LFS NATIVE REPLICATION
#REPLICATION_LISTEN_IP=0.0.0.0
# LFS BULK REPLICATION WITH WATCHDIR
#REPLICATION_LISTEN_IP=-1
#REPLICATION_WATCHDIR=/data/master/dta
#REPLICATION_LISTEN_PORT=201
#BDB_PRIVATE=on
#TUNEFORSIZE=HUGE
I haven't tried to configure it for Tokyocabinet backend. I found that for BerkeleyDB, it does not work if you disable transactions.