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

Support FUSE mountpoints #53

Open
xemul opened this issue Sep 24, 2015 · 7 comments
Open

Support FUSE mountpoints #53

xemul opened this issue Sep 24, 2015 · 7 comments
Labels
new feature no-auto-close Don't auto-close as a stale issue

Comments

@xemul
Copy link
Member

xemul commented Sep 24, 2015

Pulled from criu.org/Todo

When dumping mountpoints we explicitly check the filesystem mounted. The thing is -- not all filesystems can be just ignored on dump. E.g. FUSE mount involves a user-space daemon that is responsible for the files tree contents. If we just kill one on dump we might not be able to restore it. Need to special-care one.
@tswift242
Copy link

@xemul Any updates on this enhancement? We would like to be able to C/R FUSE mounts. Has any progress been made in this space?

@xemul
Copy link
Member Author

xemul commented Nov 7, 2017

@tswift242 , well, yes and no. We've implemented NFS mountpoints C/R which is very close to how this should be done for FUSE. The problems are a) it has been done in Virtuozzo criu branch and hasn't been pushed upstream b) FUSE needs more coding.

I would say this particular feature right now is out of direct scope for Virtuozzo, so I wouldn't count on Virtuozzo developers to implement it in the nearest future (submitting NFS patches upstream is another story, that can :) be done). What's your use-case for CRIU and FUSE? Maybe we can find the ways to make it happen.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@avagin avagin added no-auto-close Don't auto-close as a stale issue and removed stale-issue labels Jan 26, 2021
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@avagin avagin removed the stale-issue label Mar 2, 2021
@github-actions
Copy link

github-actions bot commented Apr 6, 2021

A friendly reminder that this issue had no activity for 30 days.

@buck2202 buck2202 mentioned this issue Aug 3, 2021
Closed
@github-actions github-actions bot closed this as completed Apr 6, 2022
@mihalicyn mihalicyn reopened this Apr 14, 2022
@mihalicyn
Copy link
Member

see also https://bugs.openvz.org/browse/OVZ-7283

@mihalicyn
Copy link
Member

https://lore.kernel.org/linux-fsdevel/20230220193754.470330-1-aleksandr.mikhalitsyn@canonical.com/T/#t

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new feature no-auto-close Don't auto-close as a stale issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mihalicyn @avagin @tswift242 @xemul