From: Miklos S. <msz...@in...> - 2004-07-02 15:15:24
|
> Well, just a minute ago my FS spat out "fuse internal error: inode 488 > not found" and died.. > That's not much to go on, I realize.. I don't have a reproducible case, > because it seems much harder to provoke then before the latest locking > changes.. A stack trace would be very helpful. So could you enable core file generation before starting the FS (ulimit -c unlimited), so if this ever happens again, we can look at the core file to see what happened. > By the way, have you seen fsx-linux (google search brings it right up). > It bills itself as "File system exerciser", and it causes some > troubles. Under my Reiserfs partition it runs fine, but under a FUSE > based filesystem it causes everything using the filesystem to lock up > requiring a system reset... I was able to reproduce this :). And it's independent of the rename/open races since fsx-linux is only reading and writing a single file. Miklos |