nagyist / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

failed mount #221

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I'm just starting out writing a new fuse based file system on my mac in python. 
 I have the base 
framework in place and tried to mount it... which crashed as follows

stumac-wireless:~/tmp/ronfs > ./ronfs `pwd`/mnt
fusefs@0 on /Users/sdm900/tmp/ronfs/mnt (ping DiskArb)

I noticed in /var/log/system.log

Jun 17 17:23:40 StuMac kernel[0]: MacFUSE: OUCH! daemon did not give fh 
(type=0, err=22)

Now, I can not use the directory mnt and it doesn't appear in my ls :)

stumac-wireless:~/tmp/ronfs > ls
ls: mnt: Permission denied
total 16
0 ./            0 ../           0 .svn/         8 config.ini    8 ronfs@        
0 root/         0 src/
stumac-wireless:~/tmp/ronfs > ls mnt
ls: mnt: Permission denied
stumac-wireless:~/tmp/ronfs > cd mnt
tcsh: mnt: Permission denied.
stumac-wireless:~/tmp/ronfs > rmdir mnt
rmdir: mnt: Resource busy

and as far as I can tell, nothing relating to Fuse is running

stumac-wireless:~/tmp/ronfs > ps auxww | grep -i fuse
sdm900   29348   0.0 -0.0    27328    436  p4  R+    5:34PM   0:00.00 grep -i 
fuse

Now, this is bad... I assume its time for a reboot.

Original issue reported on code.google.com by sdm...@gmail.com on 17 Jun 2007 at 9:36

GoogleCodeExporter commented 9 years ago
You know, there's a mailing list (macfuse-devel) for discussing such things. 
Repost it there and we'll talk about 
it. This area is for issues that are clearly bugs in MacFUSE Core and therefore 
are on my TODO list to be fixed.

By the way, you tried ls, cd, rmdir etc. on the failed mount directory. Did you 
try "umount `pwd`/mnt" or 
perhaps a "umount -f"?

Original comment by si...@gmail.com on 17 Jun 2007 at 5:46

GoogleCodeExporter commented 9 years ago

Original comment by si...@gmail.com on 17 Jun 2007 at 5:47

GoogleCodeExporter commented 9 years ago
yes, sorry, I didn't post the other things I did.  That gets even weirder :)

stumac-wireless:~/tmp/ronfs > umount mnt
umount: mnt: not currently mounted
stumac-wireless:~/tmp/ronfs > ls
ls: mnt: Permission denied
total 16
0 ./            0 ../           0 .svn/         8 config.ini    8 ronfs@        
0 root/         0 src/
stumac-wireless:~/tmp/ronfs > rm mnt
rm: mnt: Permission denied
stumac-wireless:~/tmp/ronfs > 

I also tried it as root

stumac-wireless:~/tmp/ronfs > sudo -s
Password:
stumac-wireless:~/tmp/ronfs > ls
ls: mnt: Permission denied
total 16
0 ./            0 ../           0 .svn/         8 config.ini    8 ronfs@        
0 root/         0 src/

As for writing to this list... its world writable and I'm not that interested 
in joining yet another mailing list.

Original comment by sdm...@gmail.com on 17 Jun 2007 at 11:32

GoogleCodeExporter commented 9 years ago
> As for writing to this list... its world writable and I'm not that interested 
in joining yet another mailing list.

"Joining" the mailing list doesn't mean it would send you email automatically. 
Just because this "list" is writable 
doesn't mean you can justify abusing it.

You need to run umount with the absolute pathname to the mount point. You are 
expressing surprise at things 
that have been discussed earlier and are documented.

Original comment by si...@gmail.com on 18 Jun 2007 at 11:01