Open rickysarraf opened 4 years ago
I found the cause. This happened because host chutzpah
was not accessible. Infact, it was not accessible because I was on a different network.
But the whole purpose of mcachefs
is the same; the ability to be able to use the cache while roaming. I hope the lag/leak was because of the crashing mcache process and that it doesn't do lookups when roaming.
Because, otherwise, (side)effectively it blocks the kernel and brings everything to a stall.
Description First of all, thank you for
mcachefs
. I believe this can serve as a caching layer for my needs where the backing store is a remote share. I am using the latestmcachefs
from the git repository. I have run into frequent crashes today. It mostly looked like a memory leak but seemed to die eventually even before OOM could come into action.If you need more information, please do mention.
OS: Debian Unstable mcache: git HEAD
Stacktrace
Mount service
Mount Config