Amit - I had previously also searched this list, as you suggested but the only place it seems to show up, you say:
"BTW, this is happening in Apple's code, not MacFUSE's, which doesn't mean it's not MacFUSE's fault. Since it's happening on a MacFUSE mount, it's very likely that it's a side effect of something going wrong in MacFUSE. " which doesn't seem an authoritative declaration of a known issue in OS X. I do see, now, that this is acknowledged as an OS X bug in a 1 line comment on - but gives no information about it. Google reveals nothing informative about the problem. I get that this is an issue in OS X and not caused by MacFUSE, but I really can't find any authoritative information on the problem or discussion of it happening elsewhere. I'm not looking to waste anyone's time. -Jeff On Nov 19, 4:29 pm, Amit Singh <[EMAIL PROTECTED]> wrote: > This is a known problem in Tiger. Search on this discussion forum, in > the *past* issues (http://code.google.com/p/macfuse/issues/list), and > perhaps Google for "vnode_rele_ext". > > MacFUSE can't help here. This can happen with other non-local file > systems. Either upgrade to Leopard or see if a workaround mentioned in > one of the search results applies to your situation. > > > panics. We're at a bit of a loss as to how to help this user out and > > gain further information, but he seems willing to help. > > > Apart from a MacFUSE issue, I would guess there is a possibility of > > bad RAM - but he seems to have issues with nothing else. > > I'd suggest always do a search first. Often, there's no need to > speculate. It'll also save you time. > > Amit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" 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?hl=en -~----------~----~----~----~------~----~------~--~---
