Closed GoogleCodeExporter closed 9 years ago
Unfortunately this looks like something that will need to be deterministically
reproducible to figure out what's
going on. Even though I tell people what 'nolocalcaches' can do, I don't want
to advocate its use because that's
not how file systems generally work in Mac OS X. Some of the associated code
paths are not well tested. This
panic could be a result of a bug either in MacFUSE or in Mac OS X.
Original comment by si...@gmail.com
on 5 Mar 2007 at 7:06
I thought that would probably be the case! I'm not familiar with debugging
kexts: is there any further
information I could gather if it happens again that would be useful?
As you probably realise, my use of nolocalcaches is based on your FAQ "picking
up remote changes".
Unfortunately one of the main things I'm using macfuse for is getting the
latest copy of constantly-growing
log files from the server so I think I do need to stick with that option. I
must have performed something like
100 similar 'copy' actions in the last few days without a hitch, though, so it
must be a relatively obscure
condition that caused the single panic.
Thanks for the great tool, anyway!
Original comment by j.m.tay...@dur.ac.uk
on 6 Mar 2007 at 8:44
Closing this as a one-off incident that's not reproducible.
Original comment by si...@gmail.com
on 8 Jun 2007 at 7:58
Original issue reported on code.google.com by
j.m.tay...@dur.ac.uk
on 5 Mar 2007 at 5:49