fsspec / fsspec/filesystem_spec

Mount using fsspec.fuse.run with AzureDatalakeFileSystem filesystem on Ubuntu 18 not working

Open
#536 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.4k
Forks
490
Avg merge
2d 3h
Merged PRs (30d)
38

Description

Hi,
I'm trying to mount an AzureDatalakeFileSystem (from adlfs python package) using fsspec.fuse.run. However, after calling the run method, I can't access the mount_point folder.
For example, I used mount_point /tmp/test1/. It looks like mount was successful, but if I try to 'ls' on the parent directory, I get: "ls: cannot access 'test1': No such file or directory"
If I cd into that folder, the folder is empty. And doing 'ls' inside that folder gets: "ls: cannot open directory '.': No such file or directory"
The only way to get the folder back to a good state is to sudo umount /test1/

I looked around and some people suggest changing directory permissions. Others suggest editing etc/fuse.conf file to include user_allow_other. But to no avail.

There is no much documentation on using run(), but I successfully created AzureDatalakeFileSystem, and I can interact with this and see the contents of the filesystem. However, run() does not seem to properly mount.
Any help or guidance here would be appreciated.
Thanks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the fsspec.fuse.run entry point and reproduce the mount on Ubuntu 18 using AzureDatalakeFileSystem; compare this with direct filesystem access, which the report says works. Done means the mount point remains accessible and lists the Azure Data Lake contents, or the failure and required setup are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, linux, python, ubuntu
Domain
cloud, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.