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

Handle unmount failures gracefully #30

Open
chrisd8088 opened this issue Jun 6, 2019 · 0 comments
Open

Handle unmount failures gracefully #30

chrisd8088 opened this issue Jun 6, 2019 · 0 comments

Comments

@chrisd8088
Copy link

@chrisd8088 chrisd8088 commented Jun 6, 2019

After running the functional test suite for a while, and encountering a hard-stop error, a number of "stale" mounts are left behind:

/dev/fuse on /GVFS.FT/test/238704f51ee541ec9049/src type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/fuse on /GVFS.FT/test/bd7025c836fa4cbe94d7/src type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/fuse on /GVFS.FT/test/f0fb2de381ea4a81a9a1/src type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

These may result when a functional test fails and doesn't clean up properly, or tries to clean up and unmount but a running process holds an open file handle within the mount.

The latter issue is one we will need to consider -- what should the action of gvfs unmount be when we cannot actually unmount the FUSE device?

@chrisd8088 chrisd8088 mentioned this issue Jun 6, 2019
31 of 31 tasks complete
@chrisd8088 chrisd8088 changed the title handle unmount failures gracefully Handle unmount failures gracefully Jun 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.