Open Kevin-Prichard opened 9 years ago
Has exactly the same problem here. Please let me know if there is any information I can give regarding this problem.
Is there any info we can provide that will help? Is there a debug switch to provide messages for you?
How about a run with strace messages?
Hi,
Sorry for the silence. Unfortunately, I'm traveling and I'm not sure when I can take care of this. One thing that you should definitely try (if you haven't yet) is a different FUSE filesystem. Sometimes the issues are in the fuse driver and not on the specific filesystem implementation. Although I have no reasons to believe that the bug is on their side, it's worth testing.
An strace could help pinpoint some issues, but if you do, make sure that you capture all threads (or even better, force it to singlethread). There's also the -o option to generate a logfile that would be worth looking at.
sudo ls /Volumes/myvol
@danunahui, thank you. I just want to copy some files from a ext4 disk. But I stuck in the same problem. The 'sudo ls' code let me sure the disk was mounted. So, I can copy the files! I tried 'sudo cd' but no work. By the way, I use 'sudo ext4fuse ...'
It's worth pointing out that whole-disk encrypted volumes hosted on ext4 filesystem probably aren't going to work with ext4fuse.
Hello, I came across this issue on OS X 10.11 El Capitan with ext4fuse @0.1.3 (fuse) and osxfuse @2.8.2 (fuse, devel) from mac ports. The ports tree is up to date and there are not outdated packages on my system. I can mount a filesystem, but then the mountpoint disappears and can not be accessed. I also get 100% used on a newly created filesystem. I am willing to gather additinal information! Thanks!
Addition: If one calls ext4fuse without using sudo, everything works fine. To be able to do that, one will need to activate the root account and then use su to get to a root shell.
@yuergen As you use sudo to mount the fs, you will not have read rights with your user, you will have su to be able to see and cd into the mount point. If you look carefully you will see that when you ls the mount point with your user, you should see something like "ls: tmp: No such file or directory", in this case I mounted my ext4 fs in a tmp folder. Regarding 100% Capacity, I believe this happens because ext4fuse only mounts disk as read only.
Same problem with El Capitan 10.11.5. The folder /Volumes or /tmp disappears. I tried sudo, su, but nothing works. I followed all the guide. (sudo dscl . append /Groups/operator GroupMembership
@rudas Thank you for pointing that out.
Tried macports ext4fuse on MacOSX Sierra, same thing, the mountpoint disappears. $ sudo ext4fuse /dev/disk2 /Users/bnilsson/ext4 -o logfile=ext4fuse.log $ mount ext4fuse@osxfuse0 on /Users/bnilsson/ext4 (osxfuse, synchronous) $ ls ext4/ ls: ext4/: No such file or directory $ sudo umount /Users/bnilsson/ext4 $ ls ext4/ ext4fuse.log
sudo ls
shows the directory and I can navigate to it as @danunahui says.
You are missing the allow_other flag: % sudo ext4fuse /dev/disk2s3 /Volumes/myvol -o allow_other
Otherwise, only root has access to the mounted volume.
After following the directions for 0.1.3 (ensured operator group membership), I tried mounting an ext4 drive from a SD card slotted into a MacBook Pro running 10.10.2.
% sudo ext4fuse /dev/disk2s3 /Volumes/myvol
After it finishes, viewing /Volumes shows the mountpoint directory has vanished. Finder also does not see it. Running
df
shows the drive, so perhaps it is registered with darwin as a filesystem-ext4fuse@osxfuse0 0 0 0 100% 0 0 100% /Volumes/myvol
But for my needs, however, it isn't really mounted. It cannot be navigated to via
cd
or seen vials
or Finder.