ndex 107e6db299e0..c0ec5a94b8d3 100644
--- a/sys/fs/fuse/fuse_vnops.c
+++ b/sys/fs/fuse/fuse_vnops.c
@@ -289,6 +289,10 @@ fuse_flush(struct vnode *vp, struct ucred *cred, pid_t pid, int fflag)
 	if (err)
 		return err;
 
+	if (fufh->fuse_open_flags & FOPEN_NOFLUSH &&
+	    (!fsess_opt_writeback(vnode_mount(vp))))
+		return (0);
+
 	fdisp_init(&fdi, sizeof(*ffi));
 	fdisp_make_vp(&fdi, FUSE_FLUSH, vp, td, cred);
 	ffi = fdi.indata;
diff --git a/tests/sys/fs/fusefs/flush.cc b/tests/sys/fs/fusefs/flush.cc
index 474cdbdb2203..7ba1218b3287 100644
--- a/tests/sys/fs/fusefs/flush.cc
+++ b/tests/sys/fs/fusefs/flush.cc
@@ -109,6 +109,36 @@ TEST_F(Flush, open_twice)
 	EXPECT_EQ(0, close(fd)) << strerror(errno);
 }
 
+/**
+ * Test for FOPEN_NOFLUSH: we expect that zero flush calls will be performed.
+ */
+TEST_F(Flush, open_noflush)
+{
+	const char FULLPATH[] = "mountpoint/some_file.txt";
+	const char RELPATH[] = "some_file.txt";
+	uint64_t ino = 42;
+	uint64_t pid = (uint64_t)getpid();
+	int fd;
+
+	expect_lookup(RELPATH, ino, 1);
+	expect_open(ino, FOPEN_NOFLUSH, 1);
+	EXPECT_CALL(*m_mock, process(
+		ResultOf([=](auto in) {
+			return (in.header.opcode == FUSE_FLUSH &&
+				in.header.nodeid == ino &&
+				in.body.flush.lock_owner == pid &&
+				in.body.flush.fh == FH);
+		}, Eq(true)),
+		_)
+	).Times(0);
+	expect_release();
+
+	fd = open(FULLPATH, O_WRONLY);
+	ASSERT_LE(0, fd) << strerror(errno);
+	// close MUST not flush
+	EXPECT_EQ(0, close(fd)) << strerror(errno);
+}
+
 /*
  * Some FUSE filesystem cache data internally and flush it on release.  Such
  * filesystems may generate errors during release.  On Linux, these get