Segmentation Fault about megafuse HOT 6 CLOSED

Can it happen because of no space in disk for megafuse to cache?

from megafuse.

The space might be what's causing the issue. Did you try to send one single big file? In that case I suspect a overflow. 2GB is 2^31 which is the maximum value for a signed int.

from megafuse.

In my case what I transferred was a bunch of "small" files (0.1MB to 400MB).
Can this happen because of /tmp/mega* fill all the disk space?

On 27/03/2015 02:00, matteo wrote:

The space might be what's causing the issue. Did you try to send one
single big file? In that case I suspect a overflow. 2GB is 2^31 which
is the maximum value for a signed int.

—
Reply to this email directly or view it on GitHub
#30 (comment).

Alexey

from megafuse.

Can this seg fault be prevented in megafuse?

from megafuse.

FYI, I posted a pull-request regarding the location of the cache. I left the default value to "/tmp" although it should probably be "/var/cache/MegaFuse" or the like.

from megafuse.

Ok, from the experience I got, the problem was indeed the space.

from megafuse.