Re: [OSXFUSE] Unmounting issues in v2.5.2

224 views
Skip to first unread message

ivenhov

unread,
Oct 10, 2012, 4:44:34 AM10/10/12
to osxfus...@googlegroups.com
Thanks Benjamin

I will try to build it and test it.
Is it only 
/Library/Filesystems/osxfusefs.fs/Support/osxfusefs.kext/Contents/MacOS/osxfusefs

that I would have to replace and then reboot?
I'm on Lion.

Daniel


On Sunday, October 7, 2012 1:56:57 AM UTC+1, Benjamin Fleischer wrote:
Hi Daniel,

The unmounting issue should be fixed in commit https://github.com/osxfuse/kext/commit/cd0621ceb510d80660879ccc90aa79f4f4db5e3c. I have not been able to reproduce any memory violation errors using OSXFUSE 2.5.2, though. 

Regards,
Benjamin

Am 02.10.2012 um 10:16 schrieb ivenhov:

Hi

I'm experiencing unmounting problems with OSXFUSE 2.5.2 but not 2.5.1
In my tests volume gets mounted fine, then accessed and unmounted but with 2.5.2 unmount takes a long time and usually comes with memory violation error.
It seems that the volume is unmounted fine and still some extra work is done in the background. 
The last thing I could see was getattr on / although that's probably irrelevant.

To unmount I'm using umount -f /Volumes/myvol command.

I think there were some changes between 2.5.1 and 2.5.2 related to race condition in unmount?
Problem is very reproducible. I'm on Lion

Thanks
Daniel

ivenhov

unread,
Oct 2, 2012, 4:16:26 AM10/2/12
to osxfus...@googlegroups.com

Benjamin Fleischer

unread,
Oct 6, 2012, 8:56:51 PM10/6/12
to osxfus...@googlegroups.com
Hi Daniel,

The unmounting issue should be fixed in commit https://github.com/osxfuse/kext/commit/cd0621ceb510d80660879ccc90aa79f4f4db5e3c. I have not been able to reproduce any memory violation errors using OSXFUSE 2.5.2, though. 

Regards,
Benjamin

Am 02.10.2012 um 10:16 schrieb ivenhov:

Benjamin Fleischer

unread,
Oct 11, 2012, 2:16:32 AM10/11/12
to osxfus...@googlegroups.com
Hi Daniel,

Correct, all you need to do is build the kernel extension from the osxfuse-2 branch and put it in /Library/Filesystems/osxfusefs.fs/Support/. Then you need to make sure that it is owned by root:wheel otherwise OS X will refuse to load it.

Regards,
Benjamin
Reply all
Reply to author
Forward
0 new messages