From: erlk o. <erl...@gm...> - 2006-05-27 13:24:46
|
Hi, is there a mean to unmout a fuse filesystem, if the daemon crashed a bit (it was stuck in an infinite "while" and "ctrl-c"-ing it didn't work) ? I can't even kill the programs that try to access the filesystem after this (even with the "-9" option and done by the "root" user). (after I did "rmmod --force fuse" and it got worse) thanks |
From: Csaba H. <csa...@cr...> - 2006-05-27 16:39:00
|
On 2006-05-27, erlk ozlr <erl...@gm...> wrote: > is there a mean to unmout a fuse filesystem, if the daemon crashed a > bit (it was stuck in an infinite "while" and "ctrl-c"-ing it didn't > work) ? I can't even kill the programs that try to access the > filesystem after this (even with the "-9" option and done by the > "root" user). I guess the filesystem daemon was still running (even if it went defunct). Have you checked if it has gone / have you tried to kill the daemon it self? Regards, Csaba |
From: Miklos S. <mi...@sz...> - 2006-05-29 10:06:33
|
> is there a mean to unmout a fuse filesystem, if the daemon crashed a > bit (it was stuck in an infinite "while" and "ctrl-c"-ing it didn't > work) ? I can't even kill the programs that try to access the > filesystem after this (even with the "-9" option and done by the > "root" user). Be sure to kill the filesystem as well! In fact killing the filesystem is usually enough, since processes blocked the filesystem will then receive an error immediately. > (after I did "rmmod --force fuse" and it got worse) Forced removal of the module should _never_ be necessary, and as you say, it just makes things worse. Miklos |