Author Archives: maru

Fixes a segfault that may occur when lessfs is used without transactions enabled. The segfault occurs when lessfs is unmounted after closing the databases. The impact of the bug is therefore low.

This release fixes some minor bugs that are related to logging only.

Lessfs now supports transactions which eliminates the need for fsck after a crash. Also new is the automatic execution of a custom script when the file system has less then a certain amount of free space left.

Lessfs with journaling. Lately I have been working on a new version of lessfs. The exciting new feature is that it does not need fsck after a crash. It’s can always recover to the last checkpoint / steady state. Would … Continue reading →

Lessfs has finally made it to 1.0.0 And even better, sourceforge tells me that it’s now stable. Only minor changes this release: Added license information at the top of every file. Updated the license information for QuickLZ after contacting the … Continue reading →

Fixes an erroneous free() that can crash lessfs upon startup when the tiger hash is selected. Changes mklessfs so that it supports automatic directory creation and database overwrites. mklessfs now has improved error reporting. And some general code cleanups.

This version of lessfs has been scrutinized for memory leaks. Several small leaks have been fixed. One small issue with lessfs_utimes has also been solved.

This release fixes two memory leaks that are related to hardlink operations and one other memory leak in file_io. It also solves a problem caused by not initializing st_[a/c/m]time.tv_nsec. Thanks to Wolfgang Zuleger for doing a great job on analyzing … Continue reading →

This release fixes some problems where permissions where not properly set on open files. It also fixes a problem with an incorrect link count of directories. Performance for some meta data operations has also improved. Working towards 1.0 stable…

This version of lessfs passes all the fsx-linux tests. It has been confirmed that this release fixes the problems that people where reporting with rsync.