On Tue, Jul 29, 2025 at 04:38:54PM -0700, Darrick J. Wong wrote:
>
> Just speaking for fuse2fs here -- that would be kinda nifty if libfuse
> could restart itself. It's unclear if doing so will actually enable us
> to clear the condition that caused the failure in the first place, but I
> suppose fuse2fs /does/ have e2fsck -fy at hand. So maybe restarts
> aren't totally crazy.
I'm trying to understand what the failure scenario is here. Is this
if the userspace fuse server (i.e., fuse2fs) has crashed? If so, what
is supposed to happen with respect to open files, metadata and data
modifications which were in transit, etc.? Sure, fuse2fs could run
e2fsck -fy, but if there are dirty inode on the system, that's going
potentally to be out of sync, right?
What are the recovery semantics that we hope to be able to provide?
- Ted
