Core functionality should be ready, need to write some tests and change up the documentation.

Tests ready now, PR should be good for review.

I didn't review everything at the moment.

@gsergey418 were you able to test mounting /mfs and interact with that directory (read/write)?

I didn't manage to test myself, simply mounting /ipfs and /ipns (using master) broke fuse in my debian VM test setup.

Would you mind updating fuse.md to reflect these changes?

@guillaumemichel Yeah, it mounts and umounts successfully on my machine and I can interact with it like a normal filesystem (ls, cat, touch, mkdir, stat, etc...). Reading and writing seems to work correctly and keeps the files intact. I've changed the variable names like you requested and added documentation.

I think it would be good to add some way of displaying the file's CID, perhaps through xattrs, if you want full MFS functionality.

Triage note: thank you, due to holiday season, we may be slower to respond, will look into this after tackling priority work for 0.35.0-rc1

Thanks @gsergey418 for the PR.

I have tested this branch on a fresh Debian Bookworm install, and it seems that most operations work great in fuse. E.g files added with ipfs add --to-files=<filename> can be listed from fuse, and files added from fuse can be listed with ipfs files.

I think it would be good to add some way of displaying the file's CID, perhaps through xattrs, if you want full MFS functionality.

I didn't manage to display a file's CID using xattrs

$ xattr /mfs/myDir/hello.txt
[Errno 95] Operation not supported: b'/mfs/myDir/hello.txt'
$ xattr /home/guissou/.ipfs/config
$ ...

The latest command works on a file outside of MFS (but I guess the file doesn't have any xattr attribute).

Is this feature working yet?

It seems that in the mounted MFS (fuse), files are readonly. It is possible to override a file, but not to edit it. It that expected? What would it take for files to be mutable?

@guillaumemichel Thank you for the review. I will look into it.

@guillaumemichel The xattr was there, you just couldn't list available xattrs because the structures didn't implement the fs.NodeListXattrer interface. I've added the support for it, so it should work now.

$ xattr mydir/
ipfs_cid
$ xattr -p ipfs_cid mydir/
QmdzR7T9jCHxQbSLPoToQPmSEoud6wEeNrQdwwk2V2fy85 

@guillaumemichel I've added some tests, but haven't run them yet, can't get it to work on my machine. I'll check it out in CI.

It seems that the FUSE sharness tests haven't been run by the CI either.

I think you need to set the TEST_FUSE env var to 1 in your CI environment.

@galargh do you know how to set TEST_FUSE=1 to enable FUSE sharness tests?

@guillaumemichel Sure! Currently, we have it disabled here - https://github.com/ipfs/kubo/blob/master/.github/workflows/sharness.yml#L49

It was disabled historically, but I'm not aware of the reasons. It might be OK to just turn it on.

Let's see if this does anything. t0300-mount.sh AFAIK is the only FUSE sharness test, I don't think it's worth inventing something new just to test this.

I think that broke some other tests in different scripts, so maybe they would have to be fixed or removed. I'm going on holiday right now, so I've won't be working on this for the next few days.

I couldn't get the FUSE tests in CI working, so probably they were disabled for a reason. I'm still going to keep those sharness tests and lib changes just in case though.

@gsergey418 do you pass the FUSE sharness tests locally?

@guillaumemichel No, they don't work either way

Awesome! :D

my todo for 0.35.0-rc1 prep

• resolve merge conflicts
• add warnings about mutable endpoint risks (undesired preload of lazy-loaded DAGs, flaky writes not ready for production)
• see if we can easily fix sharness to pass run with TEST_FUSE=1
• merge