harababurel / harababurel/gcsf

Fuse reply: Socket error OS error 57

Open
#66 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2.4k
Forks
98
PR merge metrics
No merged PRs in 30d

Description

After I have modified the .conf file adding this configuration:

  1. allow_root => commented with #
  2. mount_check = false

After a while, gcfs got finished. Macbook air version 10.11.6 - El capitan:

MacBook-Air-de-Miguel-Hernandez:Volumes Miguel$ gcsf mount /Volumes/Google/ -s "account"
INFO gcsf > Creating and populating file system...
INFO gcsf::gcsf::drive_facade > Received page 1 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 2 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 3 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 4 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 5 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 6 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 7 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 8 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 9 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 10 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 11 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 12 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 13 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 14 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 15 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 16 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 17 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 18 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 19 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 20 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 21 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 22 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 23 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 24 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 25 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 26 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 27 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 28 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 29 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 30 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 31 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 32 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 33 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 34 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 35 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 36 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 37 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 38 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 39 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 40 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 41 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 42 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 43 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 44 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 45 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 46 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 47 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 48 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 49 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 50 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 51 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 52 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 53 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 54 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 55 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 56 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 57 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 58 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 59 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 60 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 61 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 62 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 63 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 64 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 65 containing 116 files
INFO gcsf::gcsf::drive_facade > Received page 1 containing 460 files
INFO gcsf::gcsf::drive_facade > Received page 2 containing 16 files
INFO gcsf > File sytem created.
INFO gcsf > Mounting to /Volumes/Google/
INFO gcsf > Mounted to /Volumes/Google/
INFO gcsf::gcsf::file_manager > Checking for changes and possibly applying them.
INFO gcsf::gcsf::file_manager > Checking for changes and possibly applying them.
ERROR fuse::channel > Failed to send FUSE reply: Socket is not connected (os error 57)

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

Reproduce the gcsf mount on macOS 10.11.6 using the reported configuration and observe the FUSE channel error after filesystem creation. Start with the fuse::channel failure and the file_manager change-checking activity; done means the mount no longer reports that the FUSE reply socket is disconnected.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
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.