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.
-
Archives
- January 2015
- August 2014
- February 2014
- December 2013
- May 2013
- March 2013
- January 2013
- December 2012
- July 2012
- June 2012
- April 2012
- January 2012
- October 2011
- September 2011
- August 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- June 2009
- March 2009
-
Meta
How to configure lessfs to use hamsterdb?
I couldn’t find it in any documentation
About using lessfs with hamsterdb:
Please download and install hamsterdb-1.1.9 when it comes available.
In the mean time you can download it from this location : http://hamsterdb.com/public/dl/hamsterdb-1.1.9.tar.gz
Compile and install hamsterdb:
./configure; make; make install
Compile and install lessfs:
./configure –with-hamsterdb; make ; make install
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
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??
Hey, they are trying to include LessFS in Fedora15
http://fedoraproject.org/wiki/Features/LessFS
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.