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.

Sign up for GitHub

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

Jump to bottom

fuse-crash-recovery requires an implementation example that does not depend on libfuse #3

Closed
flying-122 opened this issue May 16, 2022 · 2 comments
Closed

fuse-crash-recovery requires an implementation example that does not depend on libfuse #3

flying-122 opened this issue May 16, 2022 · 2 comments

Comments

@flying-122
Copy link
Collaborator

Currently fuse-crash-recovery depends on libfuse, but in fact it has no necessary dependency on libfuse.
@flying-122 flying-122 mentioned this issue May 16, 2022
Open
@Zzzz-dot
Copy link
Contributor

support fuse crash recovery:

  1. The current implementationdoes not support fuseblk;
  2. Implement the main file system functions (some file system functions are not implemented, such as symlink);
  3. At the same time, the current implementation of the crash recovery function does not support multi-thread mode with the --clonefd option enabled, that is, crash recovery under IOCTL (FUSE_DEV_IOC_CLONE) ;
  4. If you want your custom file system to support crash recovery, you should implement the interface provided in fuse_crash_recovery_handlers struct to save the memory data structures that need to be saved after the worker process crash.

@Zzzz-dot Zzzz-dot mentioned this issue Sep 20, 2022
Merged
@flying-122
Copy link
Collaborator Author

已完成

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@flying-122 @Zzzz-dot