Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fusecompress eats up memory when reading a file #46

Closed
GoogleCodeExporter opened this issue Dec 17, 2015 · 1 comment
Closed

fusecompress eats up memory when reading a file #46

GoogleCodeExporter opened this issue Dec 17, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

I have one compressed foler, which I mount like this:

##      MOUNT THE ASP DATA STORE (COMPRESSED)
if [ `mount | grep fusecompress | grep /mnt/data/ascii | wc -l` -eq 0 ]
    then
        fusecompress -o fc_c:lzo /mnt/data/.ascii /mnt/data/ascii
fi

I then filled this folder with a bunch (~2500) of ASCII files, about
29MB each. The copying *to* this folder went smoothly, and actually
surprisingly quick.

However, when I read a file (just by copying it *from* the compressed
folder to my home directory), fusecompress quickly eats up all the RAM i
have (4G) and even more, until swap is also completely taken by
fusecompress and my machine basically crashes because there's no memory
left. The copy process never finishes.


What FuseCompress version are you using? What distribution? What kernel?
What FUSE release?

Ubuntu Lucid Lynx, AMD64.
fusecompress 2.6-2
kernel 2.6.32-22
libfuse 2.8.1

The compressed folder lies on a xfs filesystem on a software raid-0.

Original issue reported on code.google.com by hilboll@gmail.com on 19 May 2010 at 5:14

@GoogleCodeExporter
Copy link
Author

Sorry, can't help there, wrong fusecompress. Please go here: 
http://miio.net/wordpress/projects/fusecompress/

Original comment by ulrich.h...@gmail.com on 28 Oct 2011 at 2:51

  • Changed state: Invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant