First off, when reporting a panic, you should include as much information as possible, and not "snip" things. In particular, if you don't say which *specific* Mac OS X version this is, what good are the symbols? In this case, I can hit-and-trial to figure out that you're talking about 10.5.2, but I shouldn't have to.
What you're seeing is a precautionary panic induced by MacFUSE itself. MacFUSE doesn't expect this situation to occur ever, but it did, so it panics, allowing us to try to understand what could be going on. mmap isn't something you can disable in your file system. Well, you could turn off buffer caching, which would indirectly "turn off" mmap's, but you shouldn't need to do that, and that's not the solution to this problem. You've hit upon a code path that I don't expect. The file in question is "dead"--it's somehow gone away. For example, your file system could have said that the file is there; it allowed the file to be opened; and then all of a sudden it said that the file isn't there. The recourse MacFUSE has in such cases is to mark the file "dead". Most operations on such files should fail in some reasonable way. MacFUSE didn't expect fuse_vnop_mmap to be called on such files. We need to determine how that's happening. Can you easily reproduce this? If so, can you also make it happen on Tiger? Amit On Mar 3, 8:17 pm, "Amar (ಅಮರ್ ತುಂಬಳ್ಳಿ)" <[EMAIL PROTECTED]> wrote: > Hi, > I got this msg while running my userspace fs. > > --- snip --- > panic(cpu 0 caller 0x345BF44A): "MacFUSE: fuse_vnop_mmap(): called on a > dead file > system"@/Users/itsstg/macfuse-read-only/core/10.5/fusefs/fuse_vnops.c:1563 > Backtrace, Format - Frame : Return Address (4 potential args on stack) > 0x3eab7c88 : 0x12b0e1 (0x457024 0x3eab7cbc 0x13321a 0x0) > 0x3eab7cd8 : 0x345bf44a (0x345c3570 0xffffffff 0x10b000 0x1) > 0x3eab7d38 : 0x1f1eab (0x3eab7d5c 0x3eab7d6c 0x1 0x1) > 0x3eab7d88 : 0x397568 (0x76046c0 0x1 0x4e6de44 0x1) > 0x3eab7dd8 : 0x372dae (0x76046c0 0x1 0x3000 0x0) > 0x3eab7f78 : 0x3dbe77 (0x493c000 0x4e6dd40 0x4e6dd84 0x0) > 0x3eab7fc8 : 0x19f084 (0x640fcc0 0x0 0x1a20b5 0x640fcc0) > No mapping exists for frame pointer > Backtrace terminated-invalid frame pointer 0xbfffe7e8 > Kernel loadable modules in backtrace (with dependencies): > com.google.filesystems.fusefs(1.3.1)@0x345b3000->0x345c4fff > --- snip --- > > Actually I don't have mmap() implemented in our FS, but I figured that even > libfuse also don't have any mmap functions. Any idea how can i disable > mmap() in fuse. or how to handle mmap inside our fs? > > Thanks and Regards, > Amar > > -- > Amar Tumballi > Gluster/GlusterFS Hacker > [bulde on #gluster/irc.gnu.org]http://www.zresearch.com- Commoditizing > Supercomputing and Superstorage! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
