Mounting in FreeBSD 9.1 fails with "Invalid argument" about ext4fuse HOT 3 CLOSED

Hi,

Thanks for the report. In the truss output, I can see that there's a fork() call but I don't think the child is traced. Could you add that? This log print:

mount_fusefs: /dev/fuse0 on /mnt/arch: Invalid argument

seems to be written by the child. The option to pass to truss should be -f

Also, what ext4fuse version are you using?. At least I tried 0.1.2 on FreeBSD 9.1 / amd64 and had no trouble mounting simple filesystems, so overall I'd check also your fuse installation. Do other fuse based filesystem work?

BR,
Gerard.

from ext4fuse.

This is fusefs-ext4fuse-0.1.2,1 and I have also tried using the latest git version with the same result.
However, I indeed have trouble mounting with sshfs as well (which returns similar errors), so you are probably right about this not being a ext4fuse problem.

The truss output with '-f', is here [1], just in case.

[1] https://gist.github.com/4666097

Feel free to close this.

Thank you for your quick response.

from ext4fuse.

Hi,

Although you might have seen it already, this is what is failing:

1610: nmount(0x800c3a100,0xe,0x0,0x8,0xfefefefefefefeff,0x0) ERR#22 'Invalid argument'

This is the mount of the /dev/fuse device. I don't know fuse internals, but it looks like the problem is in your fuse module, since EINVAL seems to indicate that the nmount syscall fails to recognize the device. I'm basing this on what the freebsd man pages say about EINVAL here:

http://www.freebsd.org/cgi/man.cgi?query=mount&apropos=0&sektion=2&manpath=FreeBSD+9.1-RELEASE&arch=default&format=html

I'm closing this issue, feel free to reopen or open another issue if you find something later on.

from ext4fuse.