Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mount bugs on osx #1048

Open
jbenet opened this issue Apr 10, 2015 · 4 comments
Open

mount bugs on osx #1048

jbenet opened this issue Apr 10, 2015 · 4 comments
Labels
kind/bug A bug in existing code (including security flaws) topic/fuse Topic fuse

Comments

@jbenet
Copy link
Member

jbenet commented Apr 10, 2015

On OSX.

Mount fails weirdly. After being on for a while, something (possibly laptop sleep) makes the fuse mount get into an odd state. it's still mounted, but will not respond. Morever, running ipfs mount again (which should unmount before remounting) fails. It is only my forcing unmount that things recover.

@jbenet jbenet added kind/bug A bug in existing code (including security flaws) topic/fuse Topic fuse labels Apr 10, 2015
@jbenet jbenet changed the title mount fails on osx mount bugs on osx Apr 10, 2015
@opn
Copy link

opn commented Jul 13, 2015

Following the instructions here - https://github.com/ipfs/go-ipfs/blob/master/docs/fuse.md - I am having difficulty with "ipfs daemon --mount" on OSX. Latest Fuse is installed:

OSXFUSE.FuseVersion: 27
OSXFUSE.AgentVersion: 2.8.0
OSXFUSE.AgentName: OSXFUSE

and my go version is go1.4.2 darwin/amd64.

Mounting seemed to work fine - all though the structure of the two Volumes could do with a little explanation.

I get permission denied when I try to add a file with nano and then drag and drop in the Finder - I had previously changed the permissions on the mountpoints to my user), and then tried:

ipfs config Mounts.FuseAllowOther true
Error: Failed to set config value: Failure to decode config: json: cannot unmarshal string into Go value of type bool

Exiting the ipfs daemon did not seem to shut things down cleanly (see below). So I'm going to restart :)

^C
Received interrupt signal, shutting down...
Publishing!
Publishing!
07:42:29.138 ERROR     ipnsfs: leveldb: closed system.go:79
07:42:29.138 ERROR  fuse/ipns: Error Shutting Down Filesystem: leveldb: closed
 ipns_unix.go:50
david:~ BabyBlue$ ipfs config Mounts.FuseAllowOther true
Error: Failed to set config value: Failure to decode config: json: cannot unmarshal string into Go value of type bool
david:~ BabyBlue$ go version
go version go1.4.2 darwin/amd64
david:~ BabyBlue$ fuse-version
OSXFUSE.FuseVersion: 27
OSXFUSE.AgentVersion: 2.8.0
OSXFUSE.AgentName: OSXFUSE
david:~ BabyBlue$ ipfs daemon --mount
Initializing daemon...
Publishing!
Publishing!
07:51:58.078 ERROR     ipnsfs: leveldb: closed system.go:79
Error: exit status 64: mount_osxfusefs: mount point /ipfs is itself on a OSXFUSE volume
david:~ BabyBlue$ sudo umount /ipfs
Password:
umount(/ipfs): Resource busy -- try 'diskutil unmount'

@jbenet
Copy link
Member Author

jbenet commented Jul 14, 2015

I get permission denied when I try to add a file with nano and then drag and drop in the Finder - I had previously changed the permissions on the mountpoints to my user), and then tried:

are you adding via /ipns/local/...? only that part is writable atm.

we considered allowing users to write in /ipfs/... but it would force us to change workdir for the user with any write. for example:

/ > cd /ipfs/QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn
/ipfs/QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn > echo "hello world" >foo
/ipfs/QmQbWkjsp4PH3LXZJNAVFwn3pvt96bo2KKnbTQYa9RQ4aX > ls
foo
/ipfs/QmQbWkjsp4PH3LXZJNAVFwn3pvt96bo2KKnbTQYa9RQ4aX > cat foo
hello world

this is because things inside /ipfs/... are (by definition) immutable.

so the above simulates this:

> echo "hello world" | ipfs add
added QmT78zSuBmuS4z925WZfrqQ1qHaJ56DQaTfyMUF7F8ff5o
> ipfs object new unixfs-dir
QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn
> ipfs object patch QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn add-link foo QmT78zSuBmuS4z925WZfrqQ1qHaJ56DQaTfyMUF7F8ff5o
QmQbWkjsp4PH3LXZJNAVFwn3pvt96bo2KKnbTQYa9RQ4aX

@RubenKelevra
Copy link
Contributor

@jbenet can you confirm this bug for 0.8, still? Or has it been fixed in the meantime?

@Stebalien
Copy link
Member

This has not been fixed, but likely never will be. We'll close this when we finally switch to a new mount system that doesn't depend on osxfuse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) topic/fuse Topic fuse
Projects
None yet
Development

No branches or pull requests

4 participants