From: Dmitry E. O. <un...@de...> - 2008-07-04 10:53:13
|
I've encountered such a problem. When mounting a catalogue with the help of FUSE, then the amount of memory used by FUSE process increases gradually. More detailed analysis of the problem has lead me to the fact that in truth FUSE (and it doesn't depend on the type of file system, the results are approximately the same everywhere) doesn't finish the tread after it isn't needed any more. For example a few days ago I used sshfs, and today the foolowing situation can be seen: nbw:[~]$ ps -eLf|grep sshfs root 3912 1 3912 0 3 Jun23 ? 00:00:00 sshfs dimka@dgate:/share/common /share -o rw,nosuid,nodev,IdentityFile=/root/dgate,allow_other,default_permissions,reconnect root 3912 1 3913 0 3 Jun23 ? 00:00:00 sshfs dimka@dgate:/share/common /share -o rw,nosuid,nodev,IdentityFile=/root/dgate,allow_other,default_permissions,reconnect root 3912 1 3914 0 3 Jun23 ? 00:00:00 sshfs dimka@dgate:/share/common /share -o rw,nosuid,nodev,IdentityFile=/root/dgate,allow_other,default_permissions,reconnect So three threads have been opened for some days already. It would not matter, but when starting a program, creating rather big file activity, then there may appear a great amount of unfinished threads (I've seen up to 15), and if every thread uses a few (sometimes up to 10-15) megabytes then FUSE "eats up" too much memory (and it is very important for my micro-server with rather small amount of memory) Is it possible to mount with some options (may be to change *fs programme) so that non-active threads are finished automatically? PS: I've made tests on 2.4.18-2.4.25 systems and the result is the same everywhere. -- ... mpd playing: Manowar - The Demon's Whip . ''`. Dmitry E. Oboukhov : :’ : un...@de... `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537 |