Date: Mon, 24 Jan 2022 21:47:11 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261434] [fusefs] mtime and ctime changed on every read file Message-ID: <bug-261434-227-zjefpWzA0F@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261434-227@https.bugs.freebsd.org/bugzilla/> References: <bug-261434-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261434 --- Comment #7 from Alan Somers <asomers@FreeBSD.org> --- I meant, "the kernel only tries to change the file's atime". Sorry for the typo. The FUSE_SETATTR command allows the kernel to set any combination of timestamps, or none. For example, here is the debug output of a different = FUSE file system where the kernel only sets atime. 2022-01-24T21:01:26.008906Z DEBUG fuse3::raw::session: setattr unique 166 inode 3 set_attr SetAttr { mode: None, uid: None, gid: None, size: None, lock_owner: None, atime: Some(Timestamp { sec: 1643058086, nsec: 8228000 }), mtime: None, ctime: None } So it's probably an sshfs bug that it always sets mtime whenever the kernel sets atime. Have you tried reproducing on Linux? It will probably happen = if you mount with atime=3Don . --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261434-227-zjefpWzA0F>