From nobody Fri Jul 02 19:36:25 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 987EA11E52D3 for ; Fri, 2 Jul 2021 19:36:25 +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 4GGlgs3sS8z3j48 for ; Fri, 2 Jul 2021 19:36:25 +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 6D3ED1A0F3 for ; Fri, 2 Jul 2021 19:36:25 +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 162JaP3o086745 for ; Fri, 2 Jul 2021 19:36:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 162JaPNb086744 for fs@FreeBSD.org; Fri, 2 Jul 2021 19:36:25 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 19:36:25 +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 #2 from Alan Somers --- If the FUSE daemon tells the kernel that it may cache dirty data, but then = the daemon tells the kernel that the file has changed while it was dirty, then = data has been lost. Data corruption is a bug. MooseFS's hands are somewhat tied as it still uses fusefs-libs2. At that protocol level there really aren't sufficient operations for the server to manage the kernel's cache. But sshfs uses fusefs-libs3, so it ought to be = able to fix the problem. If it's possible to prove that no data corruption occurred and yet the kern= el still prints this error message, then that would constitute a bug in the kernel, and I would fix it. The most obvious way for that to happen is if = you set vfs.fusefs.data_cache_mode=3D0, completely disabling the cache. But ev= en if data_cache_mode=3D1, it wouldn't surprise me if there are cases where the w= arning is printed inappropriately; it's complicated. Especially because file attributes can be cached independently of their data. --=20 You are receiving this mail because: You are the assignee for the bug.=