Lessfs now comes with a diesel Engine. As of release 1.4.0 it also supports Berkeley DB as backend for the meta data of the filesystem. Reason for adding support for Berkeley DB is not that it was sexy to introduce it. Nor that it was fun to write the code. I needed a very reliable back-end and speed was less important then reliability. While hamsterdb still looks promising, for now it does not fulfill the requirements.
Other changes:
Lessfs now waits until it recycles deleted data chunks in the ‘blockdata’ file. This is needed because the transactional databases may revert transactions to the last steady state when lessfs is shutdown uncleanly. If the actual data has been overwritten because of reusing deleted blocks then it would be possible that after reverting the transactions the filesystem would sustain data corruption. Lessfs now waits 10 * COMMIT_INTERVAL before the space of a deleted chunk of data is reused.
Please read the release notes if you want to upgrade from lessfs-1.x to this release.
If you want to try the Berkeley DB back-end then you can find additional information in: README.berkeleydb
Enjoy,
Mark Ruijter
Interesting choice in DB’s. I was having trouble getting lessfs to work with the hamster db. I kept getting dependency errors when trying to install the RPM.
I just migrated a couple of test virtual machines over to the Berkeley DB version and despite the transfer times seeming (no actual data was collected to back this up) slower, the VMs appear (yes, this is not empirical either) faster. The memory footprint is larger upfront (I measured that), but has remained quite stable (also measured). Awesome!
neat, looks like it’s working for me. Had to modify the init script and manually copy over the lessfs.cfg-bdb.cfg though. Great work!
I’m going to turn off mlocate updatedb in cron. Is anybody else doing this? Maybe it’s just me, but it seems to run too long with lessfs.
I changed my ip and now when I run
# du -sh /fuse
I get:
du: cannot access `/fuse/.lessfs/lessfs_stats': Software caused connection abort
du: cannot access `/fuse/.lessfs/replication': Transport endpoint is not connected
du: cannot access `/fuse/veeamcp': Transport endpoint is not connected
du: cannot access `/fuse/gwbackup': Transport endpoint is not connected
1.5K /fuse
changing the IP back did not help.
Hi Richard,
Amazing, I ran into the same problem today!
Lessfs has a socket listening and thats why I think it crashes when you
change the interface.
I’ll look into it.
You could umount /fuse and remount I presume?
I stopped and restarted lessfs service and I can copy data from /fuse. I haven’t tried copying data to /fuse.
I can copy data to and from /fuse and even use vim to open a file. The only time I get errors is when I tried using du .