From nobody Fri Jul 02 20:45:40 2021 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E302611D613D for ; Fri, 2 Jul 2021 20:45:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GGnCl5wMnz3t93 for ; Fri, 2 Jul 2021 20:45:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B3A8E1AED9 for ; Fri, 2 Jul 2021 20:45:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 162Kjd9W022880 for ; Fri, 2 Jul 2021 20:45:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 162Kjd0v022879 for fs@FreeBSD.org; Fri, 2 Jul 2021 20:45:39 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 256936] Buggy filesystem detected - message wrongly triggered by FUSE filesystems Date: Fri, 02 Jul 2021 20:45:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: asomers@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256936 --- Comment #6 from Alan Somers --- Ahh, well if moosefs is indeed using fusefs-libs3, then vfs.fusefs.data_cache_mode is completely ignored. Instead, the cache behav= ior is controlled by moosefs itself. You can tell what it's requesting by look= ing 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=3D%s", args[1]->flags); } Another important thing that the server tells the kernel is the entry and a= ttr 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 f= or MooseFS. In fact, MooseFS may well be written assuming that the feature is available and working. However, it is not currently implemented in FreeBSD. --=20 You are receiving this mail because: You are the assignee for the bug.=