[Bug 256936] Buggy filesystem detected - message wrongly triggered by FUSE filesystems

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 02 Jul 2021 20:45:40 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256936

--- Comment #6 from Alan Somers <asomers_at_FreeBSD.org> ---
Ahh, well if moosefs is indeed using fusefs-libs3, then
vfs.fusefs.data_cache_mode is completely ignored.  Instead, the cache behavior
is controlled by moosefs itself.  You can tell what it's requesting by looking
at the FUSE_INIT response, either by dialing up the log verbosity (maybe,
depending on if moosefs displays it), or by running this (untested) dtrace
script at mount time

fusefs:fusefs:internal:init_done
{
    printf("flags=%s", args[1]->flags);
}

Another important thing that the server tells the kernel is the entry and attr
valid timeouts, which are returned by FUSE_LOOKUP.

Finally, there is the AUTO_INVAL_DATA feature (known as
FUSE_CAP_AUTO_INVAL_DATA in libfuse).  This would probably be very useful for
MooseFS.  In fact, MooseFS may well be written assuming that the feature is
available and working.  However, it is not currently implemented in FreeBSD.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Fri Jul 02 2021 - 20:45:40 UTC

Original text of this message