Cannot see/list mountpoint after mounting #8
Comments
|
Oh, I forgot to attach the log file. [info] [op_init:20] Using FUSE protocol 7.16 |
|
You should be able to mount the filesystem as any user that can read the filesystem device. In OSX 10.5, you can just add your user to the operator group (IIRC) that has only read permissions, which is a good thing. About the flags that you need, you might want to try something like this: Oh, and the empty ext4 filesystem should be up. I changed my home connection and forgot to configure dyndns in the new modem. |
|
For anyone else encountering this issue, I was not able to resolve it by putting myself in the operator group (I even tried rebooting the machine). However, I was able to use it just fine if I enabled the root user and mounted and used the drive as the root user. Unfortunately, I got a lot of corruptions. One time I tried copying a .sqlite3 file from my ext4 disk to my mac. The copy worked with no warnings, but when I tried to use the database, I got complaints of corruption from sqlite. I tried copying the file again, and this time it worked. However, another .sqlite3 database I tried to copy wouldn't work, no matter how many times I tried. Later I tried copying a decent size directory and got corruption errors from ext4fuse. I'd report the errors here except I've already switched back over to Linux and won't bother with Mac for the time being. Thanks Gerard for the work and I wish I could help you test more. If I go back to Mac, I'll be back :-) |
|
I assume you used fuse4x, right? I only tested with macfuse. |
|
You're correct, I used Fuse4x. IIRC, Fuse4x exists because the author of it thought that Macfuse had been abandoned, and perhaps it still worked, but I thought it was a better idea to go with something more recent. I actually don't remember though, I think I was so frustrated I tried Macfuse too, but it didn't work, but I don't remember why. |
|
Yep, actually macfuse has problems of its own with the 64 bits build. Unfortunately, I only have a OSX Leopard, and my macbook pro overheats pretty fast so it's barely usable. My primary system now is a linux installation, and ext4fuse works fine there (not that it's that useful, though). Thanks for trying, if I get my macbook pro fixed, I'll give a shot to fuse4x. I'll leave this issue open meanwhile. |
|
I tried it with OSXFuse http://osxfuse.github.com/ and I'm experiencing the same problem. |
|
10.9 Mavericks. I'm seeing the same thing here using OSX fuse as well. The partition is a 1TB in size. [info] [op_init:20] Using FUSE protocol 7.8 |
Thanks for writing this, I'm excited to try it!
I'm using ext4fuse with Fuse4X on Mac OS X Lion 10.7 x86_64 (CPU is i7-2600K). I'm able to mount the device, but then can't get to the mountpoint. I suspect it's because I'm mounting it using sudo: "sudo ./ext4fuse /dev/disk0s2 /media/LinuxDisk". This succeeds, but then /media/LinuxDisk is assigned to user and group "1000" (instead of my uesr). At such point, I can't even see the mountpoint unless I use sudo. I.e. "ls -la" doesn't work, only "sudo ls -la" does. I see that Fuse4X has mount-time options of allow_other (http://fuse4x.org/options.html#allow_other), which I suspect might help, but I dont' know where I'd specify such option. I don't know how to run ext4fuse without using sudo, is there a way? Because if so, that'd probably be a simple fix.
Thoughts?
Also, the "empty ext4 filesystem" you've linked from the Wiki Home is dead.
The text was updated successfully, but these errors were encountered: