At <http://groups.google.com/group/macfuse/msg/c760dbdca65d9be4> on October 17th I wrote:
>>> The build of 2.1.7 from >>> MacFUSE 2.1.7 (10.6 i386, x86_64).dmg at >>> <http://www.mediafire.com/?qpt4bdp0yqak7x4> >>> seems to resolve <http://bugs.wuala.com/view.php?id=2522>. At <http://groups.google.com/group/macfuse/msg/7eb27e432892f1bf> on Oct 18, 2:12 pm, Jeff Mancuso <[email protected]> wrote: >> … not designed to work well in a shared-driver environment. … >> beta and has known bugs that can lead to deadlock in somewhat >> rare situations. >> >> Drawing on experience here at ExpanDrive, we had many users >> install the non-threadsafe "unofficial" 64 bit DMG, with all >> sorts of problems. It was a decidedly "bad idea" - but nobody >> liked to hear that what seemed to run well, was actually rather >> unsafe and would eventually lead to problems. >> >> Until the developers [tuxera, mostly] get this a little farther >> along and we can all agree on … At <http://groups.google.com/group/macfuse/msg/b719be671de8f84e> on Oct 26, 6:12 am, Erik Larsson <[email protected]> wrote: > We have worked some more on the 64-bit locking and would like some > feedback on the following build: > http://www.tuxera.com/mac/macfuse-core-10.5-2.1.9.dmg > > (Despite the label it only works on 10.6 at the moment.) > This solution should be a lot more proper than the one previously > published. This build has a lot of debug code and will flood your > 'dmesg' buffer with locking-related log messages. This is useful > since if you would experience any file system lockups, you can > report the contents of the dmesg buffer to this mailing list (if > you manage to retrieve it). > > You can test it on the 32-bit kernel as well, as the same locking > solution is enabled for both kernel flavors. This build should be > much more suited for a shared environment. > _________________________________________________________________ > | Erik Larsson > | File System Developer > | Tuxera Inc. Fax: +358-98-565-7002 > | Bulevardi 2-4 A, 7th floor Email: [email protected] > | 00120 Helsinki, Finland http://tuxera.com First: thanks to Jeff for the caution, thanks to Erik and Tuxera for the further development. I'm testing (making everyday use of) MacFUSE on Snow Leopard, 32-bit kernel and extensions on a MacBook Pro. I spoke too soon on 17th October. The issue with Wuala whilst using ProtectMac AntiVirus 1.1.3 sometimes recurs, and AFAICT no build of MacFUSE works around the issue. I'm corresponding with ProtectMac Technical Support, confident that causes of the issue will be identified after I provide relevant information to them. At this stage I can't say whether MacFUSE is amongst the causes. Using different antivirus software, and the 2.1.9 Beta of MacFUSE announced by Erik/Tuxera on 26th October (.dmg dated 2010-10-20), I encountered a reproducible bug that affects a fusefs volume mounted by TrueCrypt <http://www.truecrypt.org/> 7.0a, which appears in Finder as 7.0.1. I'm prepared to report the detail of this bug -- probably to developers in the TrueCrypt area -- but first it might be useful to know whether processes owned by root are *denied* or *allowed* by TrueCrypt's use of MacFUSE. Time to go digging … -- 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.
