Lessfs-1.3.3.1 has been released

This is a bug fix release only. The most prominent bug that has been fixed was cache corruption when lessfs was used with hamsterdb. A problem with hamsterdb was also identified and solved. Hamsterdb will release 1.1.9 shortly.

p5rn7vb
This entry was posted in Uncategorized. Bookmark the permalink.

6 Responses to Lessfs-1.3.3.1 has been released

  1. Chris-U says:

    How to configure lessfs to use hamsterdb?
    I couldn’t find it in any documentation :-(

  2. Hi guys,
    Lessfs-1.3.3.1 on Ubuntu Lucid, standard config.
    Total datasize: 200GB compressed. Many small text files and many big binary files.

    Doing “du -sh /some/directories” on lessfs takes a long time (in my case 4 hours and it’s still not finished).

    Is it the normal behaviour?
    Actually what does it do when we du -sh? Does it need uncompressed the files first to calculate the disk usage?

    Thank you

  3. Sorry false alarm.
    I setup lessfs on another system and it’s fast doing du.
    Probably the disk has problem.

    Btw, on the new system I have this in /var/log/messages
    Feb 22 00:43:14 build1 lessfs[925]: Clearing path2inode cache, when this message is logged with high frequency consider raising MAX_META_CACHE
    Feb 22 01:37:34 build1 lessfs[925]: Clearing path2inode cache, when this message is logged with high frequency consider raising MAX_META_CACHE
    Feb 22 02:06:46 build1 lessfs[925]: Clearing path2inode cache, when this message is logged with high frequency consider raising MAX_META_CACHE
    Feb 22 03:24:14 build1 lessfs[925]: Clearing path2inode cache, when this message is logged with high frequency consider raising MAX_META_CACHE
    Feb 22 04:53:21 build1 lessfs[925]: Clearing path2inode cache, when this message is logged with high frequency consider raising MAX_META_CACHE

    It’s ok, right?
    However I don’t see any MAX_META_CACHE parameter in lessfs.cfg??

  4. Richard says:

    Hey, they are trying to include LessFS in Fedora15
    http://fedoraproject.org/wiki/Features/LessFS

  5. Thanks Mark for the reply.
    I’m quite happy with lessfs.
    1. The dedup is really helpful in saving space. The way users put things in our fileserver is often redundant and lessfs is the ultimate solution.
    2. The compression helps too. As the fileserver holds big number of text files.

    However, occasionally users report that when they put big files (hundreds of MB) into lessfs, the samba share got unresponsive and timed out. FYI, I activate audit feature in the samba share. What would be the reason of the timed out? Is it the samba auditing?

    Thank you.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>