Loading Profile...
NTFS-3G 2009.4.4/MacFUSE, breaks ExpanDrive
Latest version of NTFS-3G released today (2009.4.4) which now comes bundled with MacFUSE, breaks ExpanDrive. Which version of MacFUSE is compatible with ExpanDrive?
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Can you run kextstat | grep fuse
and let us know what version NTFS-3G runs?
In what way is expandrive failing exactly? -
-
Inappropriate?It should work, even with the beta. I run the beta/developer releases
-
Inappropriate?Hmmm, then why do I get a message from ExpanDrive when connecting to a SFTP site? I noticed that message after I installed the latest NTFS-3G this morning...
Time to do some more digging... -
Inappropriate?As soon as I went from MacFUSE beta, down to 2.0.3, everything is working again..
-
Inappropriate?check to see what was in Console.app related to expandrive/macfuse
-
Inappropriate?HTH:
Apr 17 10:36:14 Bruce-Garlocks-MacBook-Pro-446 ExpanDrive[404]: this MacFUSE library version is incompatible with the MacFUSE kernel extension\nException in thread Thread-3:\nTraceback (most recent call last):\n File "/expandrive/python2.5.1/lib/python2.5/threading.py", line 460, in __bootstrap\n File "/expandrive/python2.5.1/lib/python2.5/threading.py", line 440, in run\n File "/expandrive/ExpanDrive.py", line 223, in startSFTPMain\n File "/expandrive/sftp/SFTPFS.py", line 1238, in main\n File "/expandrive/pyfuse/fuse.py", line 761, in main\nFuseError: filesystem initia
Apr 17 10:36:14 Bruce-Garlocks-MacBook-Pro-446 ExpanDrive[404]: lization failed -
Inappropriate?Any news on this?
I've got the same problem here since upgrading to MacFuse 2.1.5 β two days ago.
Console says (names changed manually):
28.05.09 14:23:32 ExpanDrive[2766] EXPANDRIVE_AUTH_PASSWORD:myaccount@xyz.abc.org
28.05.09 14:23:32 ExpanDrive[2766] EXPANDRIVE_MKDIR_MOUNTPOINT:/Volumes/foobar 1
28.05.09 14:23:32 ExpanDrive[2766] EXPANDRIVE_CONNECT_PROGRESS:drive_connected
EXPANDRIVE_GET_CONFIG:volicon_path
28.05.09 14:23:32 ExpanDrive[2766] this MacFUSE library version is incompatible with the MacFUSE kernel extension -
Inappropriate?Sorry, forgot the image of the requester that's popped up:
-
Inappropriate?This should be fixed by unmounting all current MacFUSE volumes and restarting ExpanDrive.
Type mount | grep fusefs to see which are still mounted. A reboot should do it too.
If that still doesn't work, I would restart and re-install macfuse on a clean boot -
Inappropriate?Jeff is correct.
MacFUSE consists of a kernel extension, and a userspace library. When MacFUSE is upgraded both of these will be replaced with new versions. If MacFUSE is in use when the upgrade happens, then OS X will refuse to unload the kernel extension from memory. This is the error you are seeing: the old kernel extension is in memory, but the new userspace library is installed, and MacFUSE is realizing there is a mismatch when it is asked to mount something new. The volumes that are already mounted during the mismatch might seem to work, but something could be subtly wrong (we’ve seen them cause a kernel panic before.)
The official MacFUSE installer recommends rebooting after installation to avoid this issue. The ExpanDrive MacFUSE installer warns about the mismatch if the old kernel extension can’t be unloaded. Regardless, the error will go away as soon as all of the old MacFUSE volumes are unmounted.
I’m confident
-
Inappropriate?I had made a restart after installing the latest MacFuse (I had updated MacFuse from the MacFuse PrefPane). ExpanDrive was not running nor were there any MacFuse volumes mounted. "mount | grep fusefs" returned nothing (but the prompt) and a double check by reading the output of an unpiped "mount" confirmed no foreign drives in my system at the time.
I just upgraded to ExpanDrive V2 installed it and rebooted this MBP (running OS-X 10.5.7), but to no avail - same message in requester, same output in Console-log:
29.05.09 00:42:02 ExpanDrive[296] this MacFUSE library version is incompatible with the MacFUSE kernel extension
Any ideas?
Best regards
-
Inappropriate?After clearing every possible cache using OnyX and rebooting - again without success - I downgraded MacFuse via its Preference Pane (disabling betas), and boomTM, everything is working fine again (not even a reboot was needed, so the problem might be not with the kext but with the user space lib?). So there seems to be a problem in MacFuse 2.1.5 β or in the combination of my machine with it.
So everything is working again, but not with the latest MacFuse.
EMPLOYEE
EMPLOYEE
